-
-
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
1.11 Release Tracking Issue #17285
Comments
bug found: #17286 |
Can we include these two PRs for PEP 695? |
+1 for #17268 if possible |
Is it possible to add also #17357 for the experimental feature NewGenericSyntax |
Can we cherry pick #17420 ? I'm currently cutting a 1.10.1 patch release for this, so would be good to make sure that 1.11 also includes it. |
If possible, I'd like #16849 to be included! |
It looks like @koogoro cut the branch at d39f023 I'm cherry picking @picnixz 's #16849 since it fixes a crash and my #17425 since it also fixes a crash and some other issues in the new functools.partial support. This should mean everything mentioned so far will be in 1.11. Should be an exciting release :-) We may also want to cherry pick #17462 (edit: I cherry picked this as well) |
Hey, is there any expectation on when 1.11 will be released? |
Hopefully in the next week or two! |
Looks like we found an assertion error crash in the new version: #17515 |
I cherry-picked a fix to the crash from master: |
Just dropping a thanks to all the people who contributed to this release! Tons of really nice additions to the library. |
I've made the release: https://mypy-lang.blogspot.com/2024/07/mypy-111-released.html |
If we make a point release, we should include #17543 |
Should we include some kind of an easter egg for |
Can point releases include typeshed sync? (I'd like my recent distutils update to use in setuptools) Or is that against policy? |
Usually those are only included with new minor releases as the frequently also create new typing issues. |
Please include this 1.11 regression fix: (This is different from #17495.) |
I cherry picked the four commits mentioned to the 1.11 branch. |
1.11.1 is released |
Can we get bug fix release with b56f357 please? |
Will there be a mypy 1.11.2 ? the regression fixed by #17639 is holding up the |
I don't have much time for mypy right now, but if someone fixes the conflicts and makes backport PRs to the 1.11 branch that will increase your odds |
@hauntsaninja @mr-c I have created #17677 with the changes from #17675 and my request #17285 (comment) |
Okay, I've cut a 1.11.2 with the above |
It's time for the next public release!
I'll probably cut the branch at 43a605f.
If there's any fixes or really important changes you'd like to make the cut, please post them here.
The text was updated successfully, but these errors were encountered: