You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PEP 703 is coming, so GIL-less CPython builds are going to be commonplace pretty soon. What are the PyO3 maintainers' thoughts on how to support this? I'm assuming it will require some PyO3 API changes/additions, since the soundness guarantees given by CPython itself will change dramatically (e.g. Python critical sections ).
I'm keenly interested in this, since all the extensions I've built with PyO3 have been for Flask servers, where getting GIL-usage right has been very important. Just curious to see what direction you have in mind!
The text was updated successfully, but these errors were encountered:
To just comment here to add my own thoughts - we've discussed extensively in #2885 some of the likely changes that need to happen to bring nogil support. I'm very excited about PyO3 supporting nogil, and this is something I want to work on in the very near future. Before that, I am personally working on changes to make #3382 happen because I think that needs to happen for many reasons. If others want to make a start on nogil support before then, I will gladly join in reviews.
PEP 703 is coming, so GIL-less CPython builds are going to be commonplace pretty soon. What are the PyO3 maintainers' thoughts on how to support this? I'm assuming it will require some PyO3 API changes/additions, since the soundness guarantees given by CPython itself will change dramatically (e.g. Python critical sections ).
I'm keenly interested in this, since all the extensions I've built with PyO3 have been for Flask servers, where getting GIL-usage right has been very important. Just curious to see what direction you have in mind!
The text was updated successfully, but these errors were encountered: