On Jun 15, 7:59 pm, Nick Alexander <ncalexan...@gmail.com> wrote:
> > Nick is right that rebuilding the docs is a pain.  But as has been
> > pointed out before, you can rebuild the HTML version once in a new
> > branch, then only changed files get rebuilt the next time.
>
> make ptestlong does not appear to benefit from this.  I get some  
> rubbish about "configuration has changed" (why?) and then it grinds  
> for a very long time, checking every file.

I think Rob's suggestion is to do this:

sage -clone new
sage -docbuild reference html  [builds everything, takes a long time]
[edit various .py, .pyx files]
sage -b
sage -docbuild reference html  [only rebuilds html files for the
changed files]

'make ptestlong' is always going to check every file, isn't it?  And I
think you want it to: changing one .py file may have effects in
others, after all.  Maybe #5481 is relevant here?

  John

--~--~---------~--~----~------------~-------~--~----~
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
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to