schmeii

4 ms·

1. 1.▲
   by schmeii 3y ago

   There is a flag to enable it, and the default is to run with the GIL.
2. 2.▲
   by schmeii 3y ago

   This pep only affect the C world. It will not require change in Python code.
3. 3.▲
   by schmeii 3y ago

   I don't think that is possible to activate the GIL only for one thread, it has to be activated process-wide. But, if you want free-threading but you have to use an old extension that is not GIL-less, then you still can, by garding all
4. 4.▲
   by schmeii 3y ago

   Probably in the long-term the two build-mode will be merged and there will only be a "nogil" build-mode. Which doesn't mean there will be no GIL. Contrary to popular belief the goal of PEP 703 is not to remove the GIL, but on
5. 5.▲
   by schmeii 3y ago

   There already is such a mechanism in the pep. Basically there will be two build mode. The standard build that you get at python.org will work exactly as now (so with a Gil). The disable-gil build (which will most likely be available through
6. 6.▲
   by schmeii 3y ago

   That is not true. If an extension doesn't advertise that it is thread safe, the GIL get activated at runtime so it will work exactly like it does now.