Handle from foo import *
wildcard imports in Rust dep inference parser (Cherry-pick of #19249)
#19255
+104
−28
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.
This fixes #19248 by implementing explicit handling for
*
wildcard imports in the Rust-based Python dependency inference parser.The commits are somewhat individually reviewable:
insert_import
arguments are consumed from the syntax tree, forfrom ... import ...
statements in particular:name
andmodule_name
correspond toimport $name
,"$name"
,from $module_name import $name
base
andimported
correspond toimport $base
,"$base"
,from $base import $imported
from ...
part is the optional arg (before) or not (after).from ...
part and a plainimport ...
statement, than between theimport ...
part and a plainimport ...
statement, despite the superficial similarities of it! (from foo import bar
is a little likeimport foo as __secret; bar = __secret.bar
.)