-
Notifications
You must be signed in to change notification settings - Fork 677
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
0.22 release #4038
Comments
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:
***@***.***>
|
I would also be nice to have the remaining async features merged for 0.22 |
The Python 3.13 beta is out and the release manager has issued a call to action:
To help test projects which use PyO3 (and to test projects which depend on those), it would be very helpful to add support for 3.13. Free-threaded support is experimental and can come later. |
Thanks @hugovk for the ping! This is on my radar to do asap and perhaps we can even ship support for 3.13 beta 1 in 0.21.3 release so that downstream can begin testing 👍 |
@davidhewitt That would be great, and should hopefully fix jsonschema's latest dependencies for python3.13: crate-py/rpds#72 |
I think with the huge amount of work done mostly by @Icxolu and @alex (thanks both and all others who helped and reviewed!) we are complete with the GIL Ref migration work for 0.22, so in my head we can release whenever. I think there's a few various PRs and bug fixes kicking around which I hope to help review and merge in, and then maybe we can get this shipped within a week or two with 3.13 support. I think most important is #3646 which we haven't found an alternative solution to and so it feels right to me that we move ahead with that change now. |
I very much agree. I am bit pressed for time at the moment to actually carry it over the finish line though. I also think we should integrate #4097 into that PR which should be simple enough (if we do not insist on not spawning threads if the GIL is not held which could be a follow-up optimization). |
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:
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:
experimental-declarative-modules
declared stable, I think there's not a huge amount remaining to do this.The text was updated successfully, but these errors were encountered: