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
In jaraco/skeleton#143, I'm attempting to adopt more strict mypy settings for my projects. Because these checks are part of the test suite and CI checks, any failed check breaks the integration.
I'd like a way to treat mypy errors as non-blocking, to get a report of failures but not fail the check, similar to how warnings work in pytest. It would be nice if pytest-mypy could expose an option to do something similar.
I could see a number of ways to approach this need:
Have errors emitted as actual warnings.
Disable failures, but provide a separate report (similar to pytest-cov).
Treat the failures as xfail.
Maybe there are other options too.
The text was updated successfully, but these errors were encountered:
In jaraco/skeleton#143, I'm attempting to adopt more strict mypy settings for my projects. Because these checks are part of the test suite and CI checks, any failed check breaks the integration.
I'd like a way to treat mypy errors as non-blocking, to get a report of failures but not fail the check, similar to how warnings work in pytest. It would be nice if pytest-mypy could expose an option to do something similar.
I could see a number of ways to approach this need:
Maybe there are other options too.
The text was updated successfully, but these errors were encountered: