David Cournapeau, 03.02.2010 17:16: > On Thu, Feb 4, 2010 at 12:30 AM, Stefan Behnel wrote: >> BTW, I know that this is not directly comparable to other projects that use >> several separate modules. I guess there is more overhead if you have a >> larger number of small Cython modules. But that should be mitigated by >> running partial builds (which you'd certainly do during a compile-test >> cycle).
I actually really meant "partial". During development, bounded changes will only trigger a limited subset of rebuilds, so an edit-compile-run cycle will not suffer that much from small Cython modules being larger than strictly required. > Yes // builds help a lot for large projects, for example scipy - a > fully optimized scipy build takes < 2 minutes on a beefy computer, and > ~ 45 seconds for debug builds. At that point, numscons and scons > become the bottleneck. I don't care so much about complete project builds. We currently have several (Java-)builds at work that take 1-2 hours each to complete. That limits the amount of app deployments that we can run in our CI process, but it limits neither development nor unit testing. Even if we only had nightly deployments, I could still live with that. The only time when you really need a complete build is when you want to deploy an app on a (test) server, which is usually a couple of times a week. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
