Hey Andrew, Short version, the docbuild does not automatically update files as we expect it to. The surefire way to make sure the doc builds cleanly is to nuke the output/html directory and then rebuild the doc. I suspect we could delete key files in the output/html and get a partial rebuild. From what I recall, merely changing .rst (or touching them) won't rebuild the corresponding sections of the doc, be nice if it did...
Best, Travis On Friday, November 16, 2012 8:29:16 PM UTC-8, Andrew Mathas wrote: > > Hi, > > I wanted to check if I am doing something wrong because I am frequently > having problems building the sage documentation when I want to check it for > patches that I am writing or reviewing. My problem is that large sections > of the reference guide, for example, regularly fail to build. I think that > the problem may be that building the documentation does not play well with > the (sage-combinat) patch queue, although I have no real evidence for this. > Equally likely, it is something that I a doing or not doing. > > To build the documentation I typically use something like > sage -b && sage --docbuild reference html > Often this works without a hitch and just as often I get numerous warnings > like > categories.rst:44: WARNING: toctree contains reference to nonexisting > document u'sage/categories/commutative_additive_monoids' > and the corresponding pages are missing. In such cases, sage reports that > the documentation > builds "successfully" but the corresponding pages are missing. > > -- 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.
