Oooh, the GIL might be going away! <https://peps.p...
# randoma
ancient-vegetable-10556
05/12/2023, 3:48 PMOooh, the GIL might be going away! https://peps.python.org/pep-0703/
š® 3
š 2
ancient-vegetable-10556
05/12/2023, 3:52 PMnot approved yet, but Sam is targeting 3.13 for GIL-less Python to be at least an option. That would mean that future development of CPython would need to (optionally) work without the GIL
š 1
w
witty-crayon-22786
05/12/2023, 4:17 PMwhat changed since the last time we saw PEP-703?
witty-crayon-22786
05/12/2023, 4:18 PMdid it change state?
a
ancient-vegetable-10556
05/12/2023, 4:18 PMthat it was actually submitted for consideration today
ancient-vegetable-10556
05/12/2023, 4:18 PMwith a target release of 3.13
w
witty-crayon-22786
05/12/2023, 4:18 PMah, cool beans
b
bitter-ability-32190
05/15/2023, 7:48 PMYeah Sam recently said he was sending it off in a very recent comment and FYId Stu and myself š
f
flat-zoo-31952
07/21/2023, 1:54 PMhttps://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional-3-12-updates/26503/155 seems the discussion around this has kinda stalled (at least here anyways). Anybody getting any other updates about this?
b
bitter-ability-32190
07/21/2023, 2:06 PMYeah there's been like 3 threads going on in tandem. Most of them go nowhere because people can't be bothered to positively contribute new and genuine ideas.
The big news:
ā¢ Core devs voted they'd like to see free threading, and slightly positive on taking on maintenance burden
ā¢ Meta committed 3 dev years of resources to stabilization and migration for CPython if PEP 703 is accepted
ā¢ Meta also informally committed to helping make CPython faster even with PEP 703 (which was the big blocker, if any IMO. That perf got worse, and the faster CPython team would be back at square 1)
ā¢ And just recently anaconda committed to helping out the ecosystem stability
So all in all, things are trending well in PEP 703 IMO
š 1