You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting. I think this happens because right now we extract the import statements naively with the keywords start with either "from" or "import".
Quick thought on this is that we can add some logic to catch this, but it maybe quite fragile and still runs into edge cases.
Alternative is that we need a proper parser or look at the AST.
Discussed in backlog grooming that initially we'll just fix this for the base case for the time being. It would be nice to find the edge cases eventually but for now we can stick to the basic version to get it up and running
Description
Hi, it seems to be broken when the import statement has multiple lines. My imports look like this:
But in the cell that
%load_node
created, it got cut off at first line:from a import (
Context
Cell couldn't be run, had to manually fix import
Steps to Reproduce
@noklam to update
%load_node
on that specific nodefrom os import (path,
Expected Result
Full import statement in cell
Actual Result
Your Environment
pip show kedro
orkedro -V
): 0.19.3python -V
): 3.9The text was updated successfully, but these errors were encountered: