A little over a week ago I made a new branch from 7.4.beta2 for Trac 21370. I initially ran make on this branch.
For the last week, I have made changes to one file, graphs/graph_plot.py, for that ticket. For the last week, every time I run sage -b after modifying that one file, the process completes quickly. Yesterday I made a new branch from 7.4.beta4 for Trac 21458. Since it was one letter in a .rst file, I didn't run build or make on that branch. Today I switched back to the branch for 21370, made a change to that same one file, and sage -b began recythonizing. Why would recythonizing be necessary when only changing the same file on the same branch? Thanks. On Friday, September 9, 2016 at 2:48:09 PM UTC-7, Jeroen Demeyer wrote: > > On 2016-09-09 23:34, Paul Masson wrote: > > 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? > > Sorry, I don't get what you mean. Can you specify *exactly* the steps > that you do and where you think that too much is being recythonized? > -- 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.
