Hi guys, Cython is great, and everybody knows it.
I have been writing an article geared toward beginners about Python in science, and the editor asked me a for part where I talk about compiled languages and Python. While I was writing this part, striving to make it as easy as possible for beginners, it stroke me that, in my workflow, I had to write a setup.py, or a Makefile, for cython modules. On the other hand, using scipy.weave.inline, the compile step was transparent. Writing and running the setup.py breaks my worflow while developping. What are the other option for building (appart from os.system...gcc). Is there an established workflow without a separate build step. I think Sage has this, but that doesn't suite me, as I work outside of Sage. It would be great if the compile could be done at import time. For instance the first run of cython for primes.pyx could create a prime.py containing the logics to do the compilation to _primes.so, and end by cleaning up the namespace and importing everything from _primes.so. What do you think? Cheers, Gaël _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
