I'm a bit confused by your answer, because I've been seeing the same sort of behavior. For the last week I've been rebuilding a branch based on 7.4.beta2. With minor changes to one file, sage -b has been running very quickly. Today I made one minor change and the recythonizing kicked in.
In between this build and the last, I did create a new branch based on 7.4.beta4 to correct a single typo, but I didn't build that branch. Are you saying that even rebuilding the same branch while making the same sort of changes can lead to recythonizing? Or is it because I made a new branch in the meantime? Thanks. On Friday, September 9, 2016 at 12:12:40 AM UTC-7, Jeroen Demeyer wrote: > > On 2016-09-09 08:43, Marco Cognetta wrote: > > However, if I change to a > > new branch that has no changes which would necessitate recythonizing > > code, it will go through the cythonizing step again. > > What makes you think that there are no changes which would necessitate > recythonizing? > > Cython does dependency checking, so if it rebuilds something, there must > be a reason. In fact, the reason is explicitly stated when cythonizing > (with messages like building foo because it depends on bar). > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
