2008/4/14 <[EMAIL PROTECTED]>: > On Apr 14, 8:48 am, 一首诗 <[EMAIL PROTECTED]> wrote: > > > But, it is still not as fast as 1. > > > So if speed is the #1 design goal, use pure C. If not, develop in > pure Python and, if the application is too slow, profile the code and > look for bottlenecks that can be optimized. There's a good chance > that they can be resolved algorithmically, not by simply dropping down > to C. > -- > http://mail.python.org/mailman/listinfo/python-list >
Profiling python code can help spot bottlenecks that would *still be bottlenecks* if translated directly to C, so I definitely agree here...given a big enough problem space, a bad algorithm will run slow(er) regardless of language or hardware. -- Computers are like air conditioners... They quit working when you open Windows.
-- http://mail.python.org/mailman/listinfo/python-list
