> I hear about make, cmake, md5hashes, git post-commit hooks... It seems to
> me that we don't really have any problems with the current system. Its
> drawback are that a developer does have to run cython after modifying a
> .pyx files.
>
-1
+1 to make/cmake. This is the kind of manual, error-prone labour that these
systems were designed to avoid. I have fallen into the "forget to run
cython first" trap more times than I can count, and that's only going to
increase as the number of cython files increases. "If it ain't broke" could
equally (and erroneously) apply to the SVN-to-git transition and many
others. It applies in many situations, but when a system has a proven track
record of usefulness, switching to it should be strongly considered.
I have no experience with post-commit hooks, but make/cmake sounds like a
no-brainer to me.
Juan.
------------------------------------------------------------------------------
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
