Embedding Python, threading and scalability

[Aahz]

In article <mailman.1057884556.438.python-list at python.org>,
Simon Wittber (Maptek) <Simon.Wittber at perth.maptek.com.au> wrote:
>
>To write scalable applications in Python, one must write the
>'scalabilty-required' parts n C.
>
>Does anyone else see this as a problem?

Not particularly.  Most threading at the application level is done for
one or more of three purposes:

* Allowing background work and fast response in a GUI application

* Scalable I/O

* Autonomous sections of code for algorithmic simplicity (e.g.
simulations)

Python does quite well at all three out of the box (the second because
all standard Python I/O modules release the GIL, as do most 3rd-party
extensions that deal with I/O (e.g. mxODBC)).  The only thing Python
doesn't do is computational threading, and Python's overhead makes it a
poor choice for that purpose.  Finally, there are so many distributed
computing solutions that multiple processes are a viable technique for
managing computational threading.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

"Not everything in life has a clue in front of it...."  --JMS