2 ms·
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 ab
by jedberg 3y ago
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.
- samwillis 3y agoI 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.