3 ms·
Removing the GIL (in a non-braindead way) likely entails breaking all existing code using the C API. PyPy could do so without breaking cpyext, by maintaining th
by dom0 9y ago
Removing the GIL (in a non-braindead way) likely entails breaking all existing code using the C API. PyPy could do so without breaking cpyext, by maintaining the illusion of a GIL whenever control passes to cpyext.
- std_throwaway 9y agoDoes it lock the GIL so numpy can release it again immediately afterwards?
- dkersten 9y agoPerhaps it makes the unlock call a no-op before numpy tries to unlock it.
- PrimHelios 9y agoThat makes sense, I hadn't thought about the extent of the breakage.