Hi Dimitri, A few months back, Hans, Tim, Jonathan helped port most (if not all) the docstrings to Sphinx. Tim also wrote a script to generate Sphinx documentation from the docstrings (which in web2py/doc/
Than this effort stopped. The goal should be that of improving the docstrings and add references so that generated documentation does not contain errors, is easy to navigate, and contains a decent into page. This could become a replacement for epydoc. The book is not a community effort (although the community is involved with proof-reading and translations) and it will stay in latex for now. Nevertheless you can take parts of the book, convert them to sphinx and use them to improve the docstrings. Massimo On Dec 4, 8:50 am, Dmitri Zagidulin <dzagidu...@gmail.com> wrote: > Just to clarify - is the conversation here about moving the main > manual (http://www.web2py.com/examples/default/docs) to Sphinx? > Or a different set of docs, auto-generated from the code comments or > something like? > > In any case, I'd be willing to help work on it. > > On Nov 23, 10:28 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > We have had some discussion about moving the documentation to Sphinx. > > Months have passed and there has been no progress. I personally do not > > mind epydoc but some of you really liked Sphinx. > > > If you know Sphinx and want web2py to use it, please help us. > > > Massimo > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
