Skip to content

Fix cmdline package tests for namespace packages #11323

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 1 commit into from
Oct 13, 2021

Conversation

nipunn1313
Copy link
Contributor

@nipunn1313 nipunn1313 commented Oct 12, 2021

Prep for #9636

First test was failing because a was not a valid import (pkg.a was)

Second test was failing because foo.py resolved in two ways, both
as foo and foo.foo. Disambiguating the dir from the file made
mypy path work better. The error message was very clear. Came up once
foo can be a namespace package.

Confirmed that all these tests pass here - as well as on top of #9636

Prep for python#9636

First test was failing because a was not a valid import (pkg.a was)

Second test  was failing because `foo.py` resolved in two ways, both
as `foo` and `foo.foo`. Disambiguating the dir from the file made
mypy path work better. The error message was very clear. Came up once
foo can be a namespace package.
@nipunn1313
Copy link
Contributor Author

Needs rebase on #11324

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.

2 participants