You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Behave consistently when type-checking stub package directly (#21330)
Type-checking stub packages directly always worked, and people rely on
this, e.g. people run `mypy scipy-stubs` in CI. However, there is a
problem if the same exact stubs are not installed, then the incremental
mode (and therefore parallel mode) is completely busted. This is because
when computing dependencies `is_module()` returns False for these, and
therefore most dependencies are missing.
There is a simple fix however: if a module is in source set, it should
be definitely a module.
I also update some blocker error formatting in related code to be more
consistent (e.g. use capitalized errors).
f"Package '{p}' cannot be type checked due to missing py.typed marker. See https://mypy.readthedocs.io/en/stable/installed_packages.html for more details",
1580
+
f"Package '{p}' cannot be type checked due to missing py.typed marker.\n"
1581
+
"See https://mypy.readthedocs.io/en/stable/installed_packages.html for more details",
0 commit comments