> every part was designed without it in mind. Interesting, care to explain then why Python supported threading since Python2? [1] > Once again, if you are usi

> every part was designed without it in mind. Interesting, care to explain then why Python supported threading since Python2? [1] > Once again, if you are using python as a scripting language > If that's true, then you shouldn't use python. Once again, I don't. I use it as an orchestration language calling other code, and there is no good reason why the orchestration language should have an arbitrary bottleneck. Yes, the hot code isn't written in Python. That doesn't matter to this discussion. > In the "web application" example you are using, the norm is already to have many processes to handle incoming connections. Outside of the python world, it absolutely isn't. I also have numerous Go based webservices, and they don't have to jump through ICP hoops to facilitate communications between workers and services. [1]: https://docs.python.org/2/library/threading.html https://docs.python.org/2/library/threading.html