News for hackers. Stuff that matters.
Re:Our Plan for Python 3.13 by jedberg on Thursday June 15, 2023 @12:02PM (#36342473)
It's true that there are dynamic imports, but presumably it would be on the library maintainer to know about that, but also you could throw a catchable error about GIL imports or something like that.

All I'm saying is that it's solvable, and more solvable than 2 to 3.

Re:Our Plan for Python 3.13 by samwillis on Thursday June 15, 2023 @12:26PM (#36342909)
I completely agree, something like:

   from __future__ import multicore
(The proposal seems to be to call it that rather than "no Gil" as it's more positive)

And maybe if done in an __init__.py it applies to the whole module.

Do that for v3.x then drop it completely for v4

I think the issue may be that maintaining both systems is too complex.