On 05.10.2016 08:49, Rene Nejsum wrote:
As a result of past discussions, I wrote the module "xfork" which basically does this "golang
goroutine" stuff. It's just a thin wrapper around "futures" but it allows to avoid that what
René and Anthony objects about.
I had a look at xfork, and really like it. It is implemented much like the
lower level of PYWORKS and PYWORKS could build on xfork instead.
Thanks. :)
I think that the “model” of doing async should be defined in the Python
language/runtime (like in Go, Erlang, ABCL) . I the ideal case it should be up
to the runtime implementation (CPython, PyPy, Jython, IronPython etc.) how the
asynchronous behaviour is implemented (greenlets, threads, roll-it-own, etc)
That's the way I see it as well. The Python language is extremely
high-level. So, I guess in most cases, most people would just use the
default implementation.
Cheers,
Sven
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
