On Fri, Oct 12, 2012 at 11:59 AM, Jake Vanderplas <[email protected]> wrote: > sklearn is set up this way so that cython is not a build dependency for > users: we operate under the simpler the installation is for end-users, the > better (even if it causes minor headaches for developers). > > When I want to try out changes in a pyx file, I modify the file, use `cython > filename.pyx` to generate the C file, and then run setup.py
In scikit-image, we do not check in .pyx file, but call Cython at build time; this part of our build system is therefore not of much interest to you. However, when deciding whether to re-generate the Cython code, we search for filename.md5 files, and if those exist we compare them against the existing generated code. Differences cause files to be re-Cythonized. My suggestion is that you store a single .md5 file that contains the checksums of all pyx files. Whenever these change, you re-build the files. This also means that you'll always be checking in the latest version of C files (you can even have a post-commit git hook that enforces this). https://github.com/scikit-image/scikit-image/blob/master/skimage/_build.py Stéfan ------------------------------------------------------------------------------ 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
