-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add mypy to CI #177
Add mypy to CI #177
Conversation
The PR #176 adjusted GitHub CI to run against latest python versions, but the tox configuration does not respect this change. This commit updates the tox as well.
@@ -1,6 +1,6 @@ | |||
[tox] | |||
envlist = | |||
py{37,38,39,linting} | |||
py{38,39,310,311,312,linting},mypy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this mypy
environment is not running in CI.
I suggest actually that we run mypy in CI by configuring it in .pre-commit-config.yaml
instead. Here's how pytest does it:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch @nicoddemus
PR provides some type hints (as per #176) and adjusts GitHub CI to respect them.
tox
tox
configuration was updated to keep python envs consistent with GitHub CI (py37 was dropped, py311 and py312 were added)Checklist:
docs/CHANGELOG.rst
, summarizing the change and linking to the issue.pre-commit
hooks and fix any issues.pytest
and make sure no tests failed.