-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Python 3.13 tracking issue #17264
Comments
Thank you to @cdce8p for all your work towards making mypy/c work on 3.13! |
Anything I can help with? |
Note for almost all use cases mypy 1.12 and newer will work great on Python 3.13 If you're interested in helping, one thing that isn't too hard is posting a summary in the PEP 696 and 702 issues of what remains to be done based on running mypy master against the conformance test suites in https://github.com/python/typing/tree/main/conformance You could also take a look into what it would take to make mypy/mypyc work well with free threading. See mypyc/mypyc#1038. One thing here could be to look into moving mypyc to use multi-phase module init, this would also help with subinterpreters in Python 3.12 and newer |
I had a look at the PEP 702-related part of the conformance test suite and found that Mypy's master branch misses one There are still two or three |
Python 3.13 added Using it causes Edit: Turns out I forgot to update the pre-commit version of mypy. 🤦♂️ Thank you @JelleZijlstra |
@mvanderlee mypy/mypy/typeshed/stdlib/typing.pyi Line 1064 in c00f82f
|
@deprecated
) #16111ReadOnly
support for TypedDicts #17644)NamedTuple.__replace__
Support namedtuple.__replace__ in Python 3.13 #17259See Python 3.12 tracking issue here: #15277
(feel free to edit this issue)
The text was updated successfully, but these errors were encountered: