News for hackers. Stuff that matters.
Re:No-GIL mode coming for Python by miraculixx on Friday July 28, 2023 @08:34PM (#36915419)
Indeed. And the reason they use multiprocessing is bc they have learned that Python's multithreading is not a good option in cpu bound tasks. The blessing in disguise of course being that multiprocessing is also a shared nothing model, so (mostly) lock free programming is the default. Oth if you have a need for concurrently accessed shared memory/resources and need locks, it comes with an explicit cost. I think that's a good thing.

In the future the default concurrency model will be shared everything free threading, and all hell might break loose. Hopefully not.

Re:No-GIL mode coming for Python by valyagolev on Friday July 28, 2023 @08:40PM (#36915473)
IMO Python doesn't even offer enough in the way of good synchronisation primitives for the async code. I don't think the ecosystem is ready for this one.

I hope it'll be recognised by the most "host" applications (uvicorn or whatever) that multi-threading is not a good idea anyway and they'll discourage it. But there'll definitely be a macho-land of thread-"safe" programmers whose bugs we'll be downstream of