Let's Remove the Global Interpreter Lock
morepypy.blogspot.com
Let's Remove the Global Interpreter Lock
1–10 of 326 posts
Re: Let's Remove the Global Interpreter Lock
#2Just curious: if they solve it in Python, would it be possible to solve it in Ruby too ?
Re: Let's Remove the Global Interpreter Lock
#3Excellent! Where's the Donate button or call to action for businesses who want to support this? There's a small link in the sidebar to "Donation page", but that doesn't seem to have a place to donate for the remove-the-GIL effort.
Re: Let's Remove the Global Interpreter Lock
#4Just curious: if they solve it in Python, would it be possible to solve it in Ruby too ?
If I understand correctly the issue in Ruby is the existing C extensions that have been written to assume the lock exists...
Re: Let's Remove the Global Interpreter Lock
#5Excellent! Where's the Donate button or call to action for businesses who want to support this? There's a small link in the sidebar to "Donation page", but that doesn't seem to have a place to donate for the remove-the-GIL effort.
> Since such work would complicate the PyPy code base and our day-to-day work, we would like to judge the interest of the community and the commercial partners to make it happen (we are not looking for individual donations at this point).
Re: Let's Remove the Global Interpreter Lock
#6Excellent! Where's the Donate button or call to action for businesses who want to support this? There's a small link in the sidebar to "Donation page", but that doesn't seem to have a place to donate for the remove-the-GIL effort.
As mentioned in the blog post the individual donation buttons are not a resounding success. I'm happy to sign contracts with corporate donors (or even individuals) that we'll deliver. My mail should be public, if not #pypy on freenode or fijal at baroquesoftware.com
Re: Let's Remove the Global Interpreter Lock
#7Would this work with cpython extensions that were ported to PyPy?
Re: Let's Remove the Global Interpreter Lock
#8Just curious: if they solve it in Python, would it be possible to solve it in Ruby too ?
If I understand correctly the issue in Ruby is the existing C extensions that have been written to assume the lock exists...
It's the same issue with Python. AFAIK there are a number of Python libraries that are not thread-safe, and the GIL prevents them from being an issue.
Re: Let's Remove the Global Interpreter Lock
#9Would this work with cpython extensions that were ported to PyPy?
They would run under GIL (I can't see CPython C API being thread-friendly unless gilectomy succeeds)
Re: Let's Remove the Global Interpreter Lock
#10> We have some money left in the donation pot for STM which we are not using; according to the rules, we could declare the STM attempt failed and channel that money towards the present GIL removal proposal.
I didn't donate to that pot but that does seem like a judicious and reasonable step to take given the assessment of STM.