@ambv I'm interested in helping out my favorite packages but not sure where to start... I think the first step is getting the 3.12 nogil version complete? Is it going to stay in Sam Gross's GitHub?
@ambv I want to be excited but I'm so worried about another 2->3 level of transitional issues.
@ambv Only been waiting for this feature for 20 years. Lol.
@ambv What will this look like with PEP-684? It says the work can be done in parallel, but wouldn't hitting the end goal of single no-gil build mean that the subinterpreter strategy would end up having no perf benefit?
@ambv Python 4? Let's have Python 4 without GIL and with mandatory type annotations and type checking. Pretty please?;)
@jamestwebber @ambv The first step is waiting for the SC "to finalise the acceptance over the coming weeks" :)
The code will all be eventually merged upstream to the CPython repo, there's a preliminary plan: https://github.com/colesbury/nogil-3.12/wiki/PR-plan-for-PEP-703 (but let's wait for the SC plan)
In the meantime, you can test out Sam's fork. It's too early to make changes to projects based on the fork. But once upstreaming begins, early testing, prep and feedback will be important, as its essential there's community support.