yeah, best to use both! Use each tool where it is best at - and get best of both worlds!
cu, On Thu, Nov 6, 2008 at 12:53 AM, Peter Gebauer <[EMAIL PROTECTED]> wrote: > Hi guys! > > I agree, just wanted to add that many iterations over trivial code benefits > (speed-wise) tremendously from being written in C and accessed in Python, or > at least that is my experience. :) > Guess you have to weigh it against the added complexity of having to compile > C code, maybe for mulitple platforms, etc. > > On 2008-11-05 (Wed) 13:57, Greg Ewing wrote: >> Patrick Mullen wrote: >>> On Tue, Nov 4, 2008 at 12:55 AM, Greg Ewing <[EMAIL PROTECTED]> wrote: >>> >>>> The only way to improve speed is to re-code the cpu-intensive >>>> parts using something more efficent, such as C or Pyrex. >>> >>> Or, of course, write better python code if possible in those parts. >> >> Yes, certainly -- finding a better algorithm is always >> the best form of optimization! >> >> -- >> Greg >> >