Re:How fast can we make interpreted Python?
by dexterous on Wednesday June 26, 2013 @12:24AM
(#5944180)
I'm not denying that IO is important to a certain class of Python programs too; but I still can't see what leads to the conclusion that IO bound programs are the primary use case for Python. There are enough evented and async io libraries being built for just about every platform right now, that doesn't make IO the center of any of them.
Re:How fast can we make interpreted Python?
by mateo411 on Wednesday June 26, 2013 @12:48AM
(#5944261)
And then there is the GIL. So if you want to squeeze more performance out of your CPU bound task. You need to use the multiprocess module, because Python threading does not work well for CPU bound tasks.
Since you are talking about CPU-bound tasks, it is relevant that numpy array operations release the GIL.
Python is used just about everywhere for just about everything (sometimes properly, sometimes poorly). While there are a lot of web sites that run Python, there are also countless other applications that use it that are unrelated to the web. See Scipy as an example.
That said, the earlier poster mentioning that many people are using Python for IO bound processes is not too far a stretch. Why else would Twisted Python exist, and why would the new Tulip async IO stuff be developed?