A Steering Council notice about PEP 703 (Making the Global Interpreter Lock Optional in CPython)
discuss.python.org
Posting for the whole Steering Council, on the subject of @colesbury’s PEP 703 (Making the Global Interpreter Lock Optional in CPython). Thank you, everyone, for responding to the poll on the no-GIL proposal. It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details. As we’ve done a few times in the past, we ...

It’s clear that the overall sentiment is positive, both for the general idea and for PEP 703 specifically. The Steering Council is also largely positive on both. We intend to accept PEP 703, although we’re still working on the acceptance details.

Long-term (probably 5+ years), the no-GIL build should be the only build. We do not want to create a permanent split between with-GIL and no-GIL builds (and extension modules).

Short term, we add the no-GIL build as an experimental build mode, presumably in 3.13 (if it slips to 3.14, that is not a problem

  • @UlrikHDA
    5•11 months ago

    Guido once said on a podcast that if they ever ended up doing python4, removing the GIL might be one of the reason for that move. He wanted to avoid the issues we got with python2 - > 3 though. I wouldn’t worry too much.