David Cournapeau wrote: > On Wed, Feb 3, 2010 at 6:45 PM, Dag Sverre Seljebotn > <[email protected]> wrote: > > >> A project I've been thinking about is Cython-support for the waf build >> system >> > > Note that numscons gives you cython support today, if you're lazy. It > gives reliable // builds, and it known to work on quite a few > platforms. > Yes...I don't think we want to have any dependencies though (or, we maintain two test systems....). The thing about waf+Cython tools for waf is that we'd ship the thing with Cython, which is unnatural with numscons.
Bad reason perhaps... > Concerning speed of compilation, I think the main culprit for > small/moderately sized cython file is the amount of boilerplate > generated by cython (e.g. an empty cython file with just a numpy > import and cimport generates a ~ 3500 lines C file). Without knowing > much about how compilers work internally, I have observed that in > general they scale badly w.r.t. code size. Cython-generated source > file show some strange gcc behaviors as well (like compilation with > -O3 being much faster than with -O0 in some cases), I have never been > able to see a trend, though > We should have an option to split Cython-generated code into reusable include-files at some point too, and perhaps make use of precompiled headers. Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
