-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
mypy_test: Are exclude
and filter
useful?
#8139
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
Alternatively, we could have a single command-line argument, |
I'm actually somewhat inclined to remove the |
I'm fine with changing
Unrelated: I would prefer not to test our own scripts in mypy_test. Instead we should have a separate step in CI and just manually call mypy. In my view, testing stubs and testing our support script are two unrelated activities. |
This makes sense, and @hauntsaninja said something similar to me at PyCon. I'm fine with making this change. |
I generally just invoke mypy directly if I want to test just a specific file or subdirectory. I don't think it makes sense to try to reproduce all of the mypy command-line options in |
mypy_test.py
has two command-line arguments that I find somewhat useless:filter
andexclude
. (It looks like they've stayed more-or-less the same since the script's inception 7 years ago.) I'd like to get rid of them and replace them with flags that would allow me to run specific parts of mypy_test locally, instead of running the whole thing at once (e.g.--stdlib
to only test the stdlib, or--test-cases
to only test the test cases).Any objections to that?
The text was updated successfully, but these errors were encountered: