Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.4k
CI: Bump Python to 3.13 and mypy to 1.12 in mypy workflow#125592
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
sobolevn left a comment
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.
A big +1 from me :)
Eclips4 commentedOct 16, 2024
FYI: There is a PR which failed due to Python 3.11 in the mypy workflow:#125589 |
JelleZijlstra left a comment
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 "supporting" a version in the mypy issue tracker is often a bit of a misnomer. Mypy has long supported running on Python 3.12 fine; it just may not necessarily have good support for type checking all new features in Python 3.12.
JelleZijlstra commentedOct 16, 2024
We could even run it on 3.13 if we update to the latest mypy release (1.12). |
AlexWaygood commentedOct 16, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
(Mypy will still reject new-in-Python 3.12 features in some of the various directories it checks, even with this change, without changes such as the one Pablo is proposing to make to the |
AlexWaygood commentedOct 16, 2024
You get to remove a |
AlexWaygood left a comment
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.
Thanks!
d83fcf8 intopython:mainUh oh!
There was an error while loading.Please reload this page.
Eclips4 commentedOct 16, 2024
Do you think this should be backported to 3.13? |
AlexWaygood commentedOct 16, 2024
If it backports cleanly, it's nice to have a consistent "CI experience" between the actively maintained branches. But I also wouldn't spend too much time on it if it doesn't backport cleanly :-) |
Thanks@Eclips4 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry,@Eclips4, I could not cleanly backport this to |
GH-125596 is a backport of this pull request to the3.13 branch. |
…honGH-125592)* Bump mypy to 1.12 & Python to 3.13* Remove unnecessary `type: ignore`(cherry picked from commitd83fcf8)Co-authored-by: Kirill Podoprigora <kirill.bast9@mail.ru>
Eclips4 commentedOct 16, 2024
Talking about the 3.12 branch, I'm not sure if this should be done there. Running mypy on the 3.13 version may give false positives for the 3.12 version, so... what do you think? |
AlexWaygood commentedOct 16, 2024
As long as the |
Thanks@Eclips4 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
Sorry,@Eclips4, I could not cleanly backport this to |
…honGH-125592)* Bump mypy to 1.12 & Python to 3.13* Remove unnecessary `type: ignore`(cherry picked from commitd83fcf8)Co-authored-by: Kirill Podoprigora <kirill.bast9@mail.ru>
I think that we're ready to bump python to 3.12 in mypy workflow, from what I can see atpython/mypy#15277, mypy almost supports 3.12 except forpython/mypy#15313.