Skip to content

Allow importing a submodule ahead of its parent module #2237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 10, 2016
Merged

Conversation

gvanrossum
Copy link
Member

Fixes #2133.

(This is the third fix for this issue. I'm happiest with this version.)

The solution is not to bail out early when the parent module is
unavailable -- if all the imports are submodules of a package that's
acceptable (the bug was that in incremental mode it's possible that
the parent is fresh and has not been entered into the modules dict
yet, but the bail-out caused the import to be marked as missing).

Guido van Rossum added 3 commits October 10, 2016 12:41
Fixes #2133.

This is the third fix for this issue.  I think I've finally nailed it.
The solution is not to bail out early when the parent module is
unavailable -- if all the imports are submodules of a package that's
acceptable (the bug was that in incremental mode it's possible that
the parent is fresh and has not been entered into the modules dict
yet, but the bail-out caused the import to be marked as missing).
@gvanrossum gvanrossum merged commit 169b224 into master Oct 10, 2016
@gvanrossum gvanrossum deleted the fix2133alt2 branch October 10, 2016 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incremental bug involving aliases and/or nested modules or classes and/or import cycles
1 participant