> Nice! However, what exactly should we do? I guess we're not interested > in doing this for _all_ classes and modules, but only certain large > ones? Should we add a keyword in the module/class docstring that > Sphinx could pick up, indicating that the docs for this file should be > split into many pages in some predefined way? Or something more fine- > grained? In general, we should be careful not to add too much > documentation-markup into the individual source code files, I think.
While I was struggling to make Sphinx run with the correct options, Minh the Great was already building an example and creating a new thread :-D http://groups.google.com/group/sage-devel/browse_frm/thread/65c25bb4d2e94a45 Nathann -- 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
