News for hackers. Stuff that matters.

A comment on Let's Remove the Global Interpreter Lock. Parent comment

Re:Let's Remove the Global Interpreter Lock by dom0 on Monday August 14, 2017 @11:56AM (#15009596)
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.
[ Parent | on HN ]
Re:Let's Remove the Global Interpreter Lock by PrimHelios on Tuesday August 15, 2017 @12:02AM (#15015356)
That makes sense, I hadn't thought about the extent of the breakage.
[ Parent | on HN ]
Re:Let's Remove the Global Interpreter Lock by std_throwaway on Monday August 14, 2017 @03:43PM (#15012097)
Does it lock the GIL so numpy can release it again immediately afterwards?
[ Parent | on HN ]
Re:Let's Remove the Global Interpreter Lock by dkersten on Monday August 14, 2017 @04:10PM (#15012370)
Perhaps it makes the unlock call a no-op before numpy tries to unlock it.
[ Parent | on HN ]