-
-
Notifications
You must be signed in to change notification settings - Fork 352
Use tox and/or pre-commit for static analysis checks #2699
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
check.sh
is getting kinda bloated with the addition ofisort
,codespell
, andcheck_type_completeness
- and trying to read the output from it to figure out what actually failed is kind of a pain. I've been using tox and pre-commit locally to avoid having to deal with the shell scripts, and been copying over configuration and commands, and maybe it's about time to share that and maybe make it official instead.Setting up test environments in tox would also help people testing on different python versions and the like, although I've had some troubles with
test_exports/
from inside tox envs (having to mess withPY_IGNORE_IMPORTMISMATCH
, custominstall_command
s, and the like. It's definitely doable though)The text was updated successfully, but these errors were encountered: