> > > > Also part of the problem is the use of 'make' that is recommended > Yes, and there are good reasons for this. > > > I've gone back to sage -b. > Please don't, or at the very least don't ever report a bug or failing > doctest without doing "make" first. > > The problem with "sage -b" is that you *include* Sage library changes > because of a new package version but you *exclude* the actual package > changes. > > Ah, I only do this when checking out Sage library-only branches that I then merge develop into (which is okay because I am only reviewing them, not committing), for exactly this reason.
> Forget your past experiences and try again now that we have #17286. > > Okay, we'll see! That certainly should help a lot. -- 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.
