On Tue, Jan 22, 2013 at 9:53 PM, tom d <sdent...@gmail.com> wrote: > Another possible solution would be to change the error message one gets on a > failed import statement. (I also lost hair on this issue a couple days > ago.) Right now it says 'have you tried %upgrade?' or something similar; it > could include the recommendation to -sync-build.
+1 to this idea, -1 to making ./sage -b take longer. > On Sunday, January 20, 2013 7:07:00 PM UTC+3, Jeroen Demeyer wrote: >> >> On 2013-01-20 16:53, Hugh Thomas wrote: >> > Would it be a good idea for sage -b to run this automatically? On my >> > laptop, it takes just a few seconds to run sage -sync-build. >> Personally, I wouldn't like it if a few seconds were added to the time >> that ./sage -b takes. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To post to this group, send email to sage-devel@googlegroups.com. > To unsubscribe from this group, send email to > sage-devel+unsubscr...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
