A viable solution for Python concurrency

Re:A viable solution for Python concurrency by qstwall on Saturday October 16, 2021 @03:40AM (#28886228)

It is hard to see the point of a GIL removal that will destabilize the C extension ecosystem for probably a decade again:

C extensions can already start as many threads as they like. Threaded pure Python, even if GIL-less, is still slow, so what is the point?

The whole point of Python (before asyncio, pattern matching etc.) was being simple and having a nice C interface. If that continues to erode, people will (and should) look at other languages. C++ for example is pretty Pythonic these days, Java does not have these problems, Erlang (while slow) was written for concurrency from scratch, etc.

[ Parent | on HN ]

Re:A viable solution for Python concurrency by profquail on Saturday October 16, 2021 @09:48AM (#28887854)

Now could be a good time to make this change, in coordination with HPy: https://github.com/hpyproject/hpy

I agree though — it’s tempting to keep extending and stretching the language to be something it was never designed for; but at some point it’s been stretched so far it loses the properties that made it attractive to start with. I like Python, but some of the things people are using it for now, they should really consider another language instead, and write a Python wrapper on top of that if they must use it from Python.

[ Parent | on HN ]