Let's Remove the Global Interpreter Lock

Re:Let's Remove the Global Interpreter Lock by smaddox on Monday August 14, 2017 @12:09PM (#15009734)

Can't this already be handled by calling out to a C/C++ or FORTRAN procedure that processes the data in multiple threads? For number crunching, Python is almost exclusively used as glue.

[ Parent | on HN ]

Re:Let's Remove the Global Interpreter Lock by foobarchu on Monday August 14, 2017 @12:25PM (#15009887)

You CAN handle it, but why should you have to? If it's possible to remove that barrier, then it absolutely should be removed. If the only answer to a problem is "use another language", then the language in question has a limitation that needs to be addressed.

[ Parent | on HN ]

Re:Let's Remove the Global Interpreter Lock by Drdrdrq on Monday August 14, 2017 @02:44PM (#15011322)

It is not a limitation at all in this case. Python is just a front to Tensorflow and similar libraries/frameworks so GIL doesn't matter there.

[ Parent | on HN ]

Re:Let's Remove the Global Interpreter Lock by ams6110 on Monday August 14, 2017 @12:13PM (#15009780)

Today's machine learning and data science students don't know how to code in those languages. They know python, and maybe java.

[ Parent | on HN ]

Re:Let's Remove the Global Interpreter Lock by orangejewce on Monday August 14, 2017 @02:32PM (#15011200)

Don't forget R... shudders

[ Parent | on HN ]

Re:Let's Remove the Global Interpreter Lock by sin7 on Monday August 14, 2017 @02:47PM (#15011367)

What's wrong with R? I know it's not a programmers language but it's great for getting things done.

[ Parent | on HN ]