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 #620

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

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

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

Comments

@ascillitoe
Copy link
Contributor

#619 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.
@ascillitoe ascillitoe added the Type: Maintenance Anything to do with library maintenance (CI, linting, refactoring etc.) label Sep 15, 2022
This was referenced Sep 15, 2022
Merged
Merged
@ascillitoe ascillitoe mentioned this issue Sep 29, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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 Python 3.10.6 pin
1 participant
@ascillitoe