Hacker News Reader

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.

View on HN

That makes sense, I hadn't thought about the extent of the breakage.

Does it lock the GIL so numpy can release it again immediately afterwards?

Perhaps it makes the unlock call a no-op before numpy tries to unlock it.

Reply on news.ycombinator.com