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 ...
  • schmieroslav
    1·
    1 year ago

    I don’t quite grasp the immediate consequences of this - does this mean that I can use threads instead of subpeocesses if I want to parallelize my program beyond one core?

    • maggio
      2·
      1 year ago

      I also don’t know much about this subject, but I found this introduction quite helpful: What Is the Python Global Interpreter Lock (GIL)?

      Further down it does mention that currently you would use multiple processes (each one having its ownn GIL) to do this, but I guess this would allow you to use threads instead, if I understand it correctly