-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
dmypy crashes on checking a couple files #18019
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
Comments
Can repro. The full exception when running dmypy as module with a fresh master checkout:
|
Git bisected this error to 98a22c4 Though, it's most likely not that commit at fault by iteself, but an interraction with dmypy, or incremental checking. |
Fixes #18019 Fixes #17775 These two are essentially variations of the same thing. Instead of adding e.g. `types` to `SENSITIVE_INTERNAL_MODULES` (which would be fragile and re-introduce same crashes whenever we add a new "core" module) I add _all stdlib modules_. The only scenario when stdlib changes is when a version of mypy changes, and in this case the daemon will be (or should be) restarted anyway. While adding tests for these I noticed a discrepancy in `--follow-imports=normal` in the daemon: the files explicitly added on the command line should be always treated as changed, since otherwise we will not detect errors if a file was removed from command line in an intermediate run. Finally the tests also discovered a spurious error when cache is disabled (via `/dev/null`).
Crash Report
While trying to make a minimal repro of another bug, I noticed this reliable crasher
Traceback
To Reproduce
Your Environment
mypy.ini
(and other config files):The text was updated successfully, but these errors were encountered: