William Stein <wst...@gmail.com> writes: > On Mon, Feb 20, 2012 at 10:06 AM, Keshav Kini <keshav.k...@gmail.com> wrote: >> Robert Bradshaw <rober...@math.washington.edu> writes: >>> Cython is just a py(x) to C compiler. The problem is not Cython per >>> se, but re-building when changing branches. Each "clone" keeps it's >>> own independent set of build artifacts, so switching between them does >>> not require a re-build. >> >> Sure, that much I certainly understand. I don't know what William is >> saying about dependency checking, though. > > If you switch between git branches all the build artifacts are for the > branch right > *before* you did the switch. It would seem likely this could confuse > the hell out > of Pyrex, but maybe not Cython (?). Even if it doesn't confuse > them, it can cause > huge build times -- e.g., each time you switch branches, you might have to > wait > 30 minutes for "sage -br", in case the branches touch something that is > depended > on by a lot of other Cython code. The Sage version of branches > completely solves > this problem. >
OK, why not cache object files by hashes of input or something? Of course I'm probably vastly underestimating the complexity of this problem... -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
