There are some global dependencies, most notably setup.py. So if you change that then every *.pyx file is re-cythonized, and hence gcc called on every one of them. If there was no change to the Cython output then gcc should answer everything from ccache, so it would still be fast. Of course you really have to work if the Cython output *did* change.
On Saturday, June 7, 2014 8:08:10 AM UTC+1, Ralf Stephan wrote: > > On Monday, May 12, 2014 11:36:20 AM UTC+2, P Purkayastha wrote: >> >> ... It shouldn't have upgraded anything, but it still decided to compile >> a bunch of packages anyway. >> > > I have witnessed the same thing recently. Someone with knowledge of the > code please correct me. I think what is probably happening is that > $HOME/.cycache over time fills with old entries. Some get cleaned but the > ones not getting cleaned fill up, until the cleanup process is cleaning a > part of the previously cached files every time a major build happens. > > The obvious workaround is to rm -rf $HOME/.cycache when this occurs. > > Regards, > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
