0.22 release

[davidhewitt]

Now that 0.21 and 0.21.1 are out the door, I think we can let main start merging breaking changes heading towards the 0.22 release. I will deal with any patch releases as cherry picks from here on out.

There's a couple of must-do items for 0.22:

• The cleanups for the GIL Refs migration for 0.22, listed in GIL Refs API Removal - Tracking Issue #3960
• The TLS soundness fixes in Close TLS-based soundness holes by running closure on a newly created thread. #3646

I also left a few items in the milestone which I thought made sense to look at soon-ish. I'll be looking at some of those - https://github.com/PyO3/pyo3/milestone/14. If anyone is interested in taking on some of these, please ping here, on those issues, or on Discord and I can gladly share any thoughts / notes with you and be a reviewer instead of the implementer 😄

Finally, I'm going to start writing some more high-level issues summarising topics where potential contributors might want to get involved. There are many areas where I think PyO3 can improve and just needs someone with the time and interest.

Along that line, these are some of my nice-to-haves for 0.22:

• I would love to see experimental-declarative-modules declared stable, I think there's not a huge amount remaining to do this.
• MSRV bump (cc @alex who I think had one prepped). Was it 1.62 or 1.63 we agreed as the target? Update MSRV to 1.63 #4129
• I'm planning to figure out a roadmap to get to Python 3.13's "freethreaded mode" support. I think this will consume the vast majority of my available time over the coming weeks.

[alex]

1.63 (this should let us drop parking_lot)

…

On Tue, Apr 2, 2024, 4:51 PM David Hewitt ***@***.***> wrote: Now that 0.21 and 0.21.1 are out the door, I think we can let main start merging breaking changes heading towards the 0.22 release. I will deal with any patch releases as cherry picks from here on out. There's a couple of must-do items for 0.22: - The cleanups for the GIL Refs migration for 0.22, listed in #3960 <#3960> - The TLS soundness fixes in #3646 <#3646> I also left a few items in the milestone which I thought made sense to look at soon-ish. I'll be looking at some of those - https://github.com/PyO3/pyo3/milestone/14. If anyone is interested in taking on some of these, please ping here, on those issues, or on Discord and I can gladly share any thoughts / notes with you and be a reviewer instead of the implementer 😄 Finally, I'm going to start writing some more high-level issues summarising topics where potential contributors might want to get involved. There are many areas where I think PyO3 can improve and just needs someone with the time and interest. Along that line, these are some of my nice-to-haves for 0.22: - I would love to see experimental-declarative-modules declared stable, I think there's not a huge amount remaining to do this. - MSRV bump (cc @alex <https://github.com/alex> who I think had one prepped). Was it 1.62 or 1.63 we agreed as the target? - I'm planning to figure out a roadmap to get to Python 3.13's "freethreaded mode" support. I think this will consume the vast majority of my available time over the coming weeks. — Reply to this email directly, view it on GitHub <#4038>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAGBGG5X3ZBAJDM6WBANLY3MK55AVCNFSM6AAAAABFUCWSJ6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCNBSGM2TSNQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[wyfo]

I would also be nice to have the remaining async features merged for 0.22