Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Monitor mypy releases and revert to Python 3.10 in CI when issue fixed #763

Closed
ascillitoe opened this issue Sep 15, 2022 · 0 comments · Fixed by #795
Closed

Monitor mypy releases and revert to Python 3.10 in CI when issue fixed #763

ascillitoe opened this issue Sep 15, 2022 · 0 comments · Fixed by #795
Labels
Effort: XS Type: Maintenance Anything to do with library maintenance (CI, linting, refactoring etc.)

Comments

@ascillitoe
Copy link
Contributor

#761 explicitly sets our CI to use Python 3.10.6 until this issue is fixed. We should monitor the upcoming mypy 0.980 and 0.990 releases and revert to setting 3.10 in CI once the issue is fixed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Effort: XS Type: Maintenance Anything to do with library maintenance (CI, linting, refactoring etc.)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Revert "Temporary fix for mypy issue in Python 3.10 CI (#761)"
1 participant
@ascillitoe