Re:Let's Remove the Global Interpreter Lock
by rguillebert on Monday August 14, 2017 @12:43PM
(#15010097)
C extensions will still run under the GIL
Re:Let's Remove the Global Interpreter Lock
by int_19h on Tuesday August 15, 2017 @02:27AM
(#15015984)
Given the amount of C extension code running in a typical large Python app these days, isn't this basically defeating the purpose?
Re:Let's Remove the Global Interpreter Lock
by rguillebert on Tuesday August 15, 2017 @08:11AM
(#15017434)
It really depends on the use case I think
What python doesn't have is a C api for extensions that makes sense without a GIL. So ideally a correct threadsafe C extension will continue to be correct, which probably implies that a function called "PyEval_AcquireLock" will continue to provide similar guarantees. Which means that the process for utilizing more cores with pure python code in one process will probably be a gradual upgrade process.