sturlamolden wrote: > Robin Becker wrote: > >> it's probably wonderful, but I don't think I can ask people to add numpy to >> the >> list of requirements for reportlab :) > ........ > This was Matlab, but the same holds for Python and NumPy. The overhead > in the first code sniplet comes from calling the interpreter inside a > tight loop. That is why loops are the root of evilness when doung CPU > bound tasks in an interpreted language. I would think that 9 out of 10 > tasks most Python users think require a C extension is actually more > easily solved with NumPy. This is old knowledge from the Matlab > community: even if you think you need a "MEX file" (that is, a C > extension for Matlab), you probably don't. Vectorize and it will be > fast enough. >
I think you're preaching to the converted. The very first serious thing I did in python involved a generational accounting model calculation that was translated from matlab into Numeric/python. It ran about 10 times faster than matlab and about 5 times faster than a matlab compiler. -- Robin Becker -- http://mail.python.org/mailman/listinfo/python-list
