PEP 703: Making the Global Interpreter Lock Optional

PEPs
122

FYI: The steering committee decided that “We intend to accept PEP 703, although we’re still working on the acceptance details.”

A Steering Council notice about PEP 703 (Making the Global Interpreter Lock Optional in CPython)

4 Likes
123

The steering council has now formally accepted PEP 703:

12 Likes
124

FYI: The tracking issue for PEP 703 implementation in Python: PEP 703 -- Making the Global Interpreter Lock Optional in CPython · Issue #108219 · python/cpython · GitHub

4 Likes
125

Has the no-gil code been fully merged to main at this point or is there more to do? I’ve tried configuring with and without --disable-gil and was mildly surprised not to see a change in the number of test cases run. I would have expected to see some new test cases.

126

It’s work in progress.

Follow this issue for the current state:

3 Likes
127

Thanks. I now recall that, but must have lost track of it with all the other chit-chat (a couple threads with ~250 posts).

128

The PEP also lists a HOWTO, which doesn’t seem to be present still: PEP 703 – Making the Global Interpreter Lock Optional in CPython | peps.python.org and don’t see it in the tracking issue. Is there a good place for docs on it, especially how to start supporting it from extensions?

4 Likes
129

@ngoldbaum is working on a guide for porting extensions and I am also working on the HOWTO.

11 Likes
130

@colesbury Has there been any progress on the HOWTO? It would be great to read this, and to share with the community to bring more people in for testing free threaded builds. Thanks for your work!

1 Like
131

Yes, there are two HOWTO guides:

4 Likes