1.11 Release Tracking Issue

[koogoro]

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.

[koogoro]

bug found: #17286
edit: not a bug! 🎉

[JelleZijlstra]

Probably good to include #17284 and #17292

[cdce8p]

Can we include these two PRs for PEP 695?

• [PEP 695] Support recursive type aliases #17268
• [PEP 695] Detect errors related to mixing old and new style features #17269

[tusharsadhwani]

+1 for #17268 if possible

[DanieleIsoni]

Is it possible to add also #17357 for the experimental feature NewGenericSyntax

[ngnpope]

Would love #17371, #17376, and #17382 if possible.

[hauntsaninja]

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.

[picnixz]

If possible, I'd like #16849 to be included!

[hauntsaninja]

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)

[hxyannay]

Hey, is there any expectation on when 1.11 will be released?
Really waiting forward to the new features :)

[koogoro]

Hey, is there any expectation on when 1.11 will be released? Really waiting forward to the new features :)

Hopefully in the next week or two!

[svalentin]

Looks like we found an assertion error crash in the new version: #17515