On Mon, Oct 15, 2012 at 01:18:11PM +1100, Juan Nunez-Iglesias wrote: > +1 to make/cmake.
Just to make it clear: adding a dependency on make or cmake is just not an option. These tools are not part of the standard Python build chain. The reason why we are checking in the C files is that we want to avoid having a dependency on Cython. We are striving to have a low dependency package. This is an important goal of scikit-learn, and part of its success. I don't think that a system running Cython to regenerate C files based on timestamp is an option. Indeed, because timestamps are not a reliable indicator, it would run too often, and we would end up with new C code checked in git by mistake. For the similar reasons, I'd like running Cython to be something manual, not automatic. As too many things depend on the Cython version, the operation of running Cython is not benine. I'd like the developers to be aware of it. My 2 cents, Gaël ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
