Fix numpy go-to-definition by taking it off autoimport list for this case #447
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
numpy
is in the autoimport list, I think go to definition doesn't use the pure static strategy of jedi'sgoto
and sees that, e.g.,numpy.ones
has__module__
set tonumpy
and uses that, while the static strategy correctly sees thatones
is defined innumpy.core.numeric
. To fix, in this PR we take everything off the jedi autoimport list before usinggoto
for GTD, and we restore it once we're done.Test plan: added a unit test that passes with this PR and fails without this PR.