- cross-posted to:
- python@programming.dev
- hackernews@derp.foo
- technews@radiation.party
Meta is dedicating 3 engineers to get the nogil patches into cpython. There are some other companies stepping up as well. This is huge this is the closest we have ever been to solving the issue of the GIL.
teraflopsweat ( @teraflopsweat@lemm.ee ) 6•2 years agoAs a filthy casual, could anyone give me a link or brief summary as to why the GIL should/shouldn’t go away?
verdare [he/him] ( @verdare@beehaw.org ) English3•2 years agoThis proposal was linked in the page above, and I think the first few sentences do a pretty good job of summarizing the problem.
verdare [he/him] ( @verdare@beehaw.org ) English5•2 years agoFor the amount of multiprocess code I’ve written in Python, I’m embarrassed that this is the first I’m hearing about the noGIL build. Really excited to see this feature become the default, though it looks like it will take a while. GIL has definitely been a pain in the ass for fully utilizing multi-core systems.
doot ( @doot@social.bug.expert ) English4•2 years agocan’t wait to try it out