5 ms·

CPython doesn't have any reservations about breaking the Python API between minor versions, so why care about the C API? I get where you're coming from, but the

CPython doesn't have any reservations about breaking the Python API between minor versions, so why care about the C API? I get where you're coming from, but they've already shown they don't care much for compatibility, so I don't see why that's a big obstacle.

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 ago
  Does it lock the GIL so numpy can release it again immediately afterwards?
  - dkersten 9y ago
    Perhaps it makes the unlock call a no-op before numpy tries to unlock it.
- PrimHelios 9y ago
  That makes sense, I hadn't thought about the extent of the breakage.