-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
--disallow-incomplete-defs does not print errors when run without this argument previously #4913
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
This is likely caused by the switch to incremental mode by default (may be a problem with import cycles). As a temporary workaround you can use |
I managed to produce a minimal test case:
|
I'm guessing that |
Maybe this was fixed by #5414? My suggestion was implemented there. |
I'll check when I get home. |
This bug is reproducible with mypy 0.620, but not with mypy HEAD. Closing. |
I have a fairly large project that is partly type-checked. Using the following
mypy.ini
file it typechecks without errors:Running it with
--disallow-incomplete-defs
or--disallow-untyped-defs
still produces lots of warnings.Since upgrading to mypy 0.590, running
mypy
, followed bymypy --disallow-incomplete-defs
will not output any warnings, although the latter command should produce loads.mypy --disallow-untyped-defs
on the other hand still works. When runningmypy --disallow-incomplete-defs
after removing.mypy_cache
or aftermypy --disallow-untyped-defs
, it will again print the warnings, until the next timemypy
is run without arguments.--no-incremental
also works around this problem.I tried to create a minimal test case with just one file exhibiting that problem, but unfortunately that worked correctly.
I tested it with Python 3.5.5.
The text was updated successfully, but these errors were encountered: