-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Cache causes mypy to fail every 2nd run for module importing from google.cloud #12232
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
Labels
bug
mypy got something wrong
Comments
hauntsaninja
pushed a commit
to hauntsaninja/mypy
that referenced
this issue
Feb 24, 2022
Fixes python#12232 Another "fail every 2nd run" bug
Perfect, thanks. Opened a fix in #12250. In case you need a quick fix, the bug here is sensitive to ordering, so if you reorder your imports, things should work. |
Thank you very much. I use |
hauntsaninja
pushed a commit
to hauntsaninja/mypy
that referenced
this issue
Feb 24, 2022
Fixes python#12232 Another "fail every 2nd run" bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
I have a project that imports things from
google.cloud
, which is a namespace package as far as I know. In a certain, very specific configuration mypy fails on every second run. This is very similar to #9852. However, this bug affects the most recent mypy, 0.931. Since the reproducer of #9852 is fixed, I was asked to open a bug report here.To Reproduce
The following script does reproduce the problem on Debian Stable and inside the Docker image
python:latest
.Expected Behavior
Pass or fail every time. I am not sure what would be correct in this case.
Actual Behavior
Mypy accepts and rejects the code every 2nd run.
Your Environment
Debian Stable and
python:latest
. The reproducing script should cover all relevant details.The text was updated successfully, but these errors were encountered: