On Fri, Oct 05, 2012 at 09:15:29PM -0400, Kenneth C. Arnold wrote: > Another option: ignore them in development branches and add them back in the > release branches.
The goal is that anybody cloning the master branch of the scikit should be able to build the scikit without the cython. > This would also make cherry picking from the development branch less > likely to have merge conflicts. Indeed, and this is a good reason to do commits of generated code in separate commits. I don't do it, but I should. Thanks for your thoughts, 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
