Paul Moore wrote:
I don't know *that* much about Erlang, but Python's model is that of a single shared address space with (potentially multiple) threads of code running, having access to that address space.
I don't know much about Erlang either, but from what I gather, it's a functional language. That removes a lot of potential problems with concurrency right from the beginning. You can't have trouble with mutation of shared state if you can't mutate state in the first place. :-) -- Greg _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
