Hi Johan, On 3 Aug., 09:36, "Johan S. R. Nielsen" <j.s.r.niel...@mat.dtu.dk> wrote: > Oh, yes, I see: "sage -b" does indeed only build changed files and > their dependencies; I must have been working on a quite fundamental > module last time I tried. Why doesn't the Developer's Guide refer to > "sage -tnew" for when doc-testing?
This would be dangerous. Typically, if a patch causes problems, then it is a problem in the doctests of a completely different file. Example: I recently had a change in the GAP interface representation of cyclotomic fields (so, I changed sage/rings/number_field/). As a result, a doctest in sage/ interface/gap broke. But the reason was in fact a bug in the PARI interface. Those things would be impossible to find without full doctesting. Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
