-
-
Notifications
You must be signed in to change notification settings - Fork 485
mypy crash when .mypy_cache is present #423
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
@danifus I've encountered the same problem, reinstalling both |
@danifus fixed, sorry for the delay, I'm a bit busy with GSoC stuff at the moment |
Thanks! That was actually super quick! It's great to be able to use incremental mode again :D |
Any news on a new release containing this fix? Even if |
What's wrong
Under certain circumstances, a project with a typing error will produce correct mypy errors and hints when
.mypy_cache
is not present but a stack trace if it is.Here is a simplified reproduction repo demonstrating this behaviour: https://github.com/danifus/djstubs-reproduce2
django
anddjango-stubs
cd
to directory containingmypy.ini
mypy . --tb
mypy . --tb
The first
mypy . --tb
produces:The second run produces:
This behaviour occurs if the error is in either
test_app/models.py
orsecond_app/models.py
(it currently is only insecond_app/models.py
).How is that should be
Every run should produce the same (initial) output
System information
python
version: 3.7django
version: 3.0.8mypy
version: 0.770django-stubs
version: 1.5The text was updated successfully, but these errors were encountered: