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
Currently we find all the imports and class defs in the module and treat them as all "in scope" for any annotated function
So there are some edge cases where we would fail to auto-add an import because we treated a non-top-level classdef or import elsewhere in the module as in-scope, whne it wasn't
It looks like Parso is able to keep track of variable scopes in its parse tree... so we could potentially "get this right", just at the cost of even more complication in our auto-import logic...
The text was updated successfully, but these errors were encountered:
Currently we find all the imports and class defs in the module and treat them as all "in scope" for any annotated function
So there are some edge cases where we would fail to auto-add an import because we treated a non-top-level classdef or import elsewhere in the module as in-scope, whne it wasn't
It looks like Parso is able to keep track of variable scopes in its parse tree... so we could potentially "get this right", just at the cost of even more complication in our auto-import logic...
The text was updated successfully, but these errors were encountered: