I would like to generate printed Python documentation in my own very compact
spartan format ("save a tree!"). Since I'm quite familiar with LaTex etc., if I
could run just the parser on the sources of the standard Python documentation
(for instance, on the tutorial), then I would use the resulting tree as a
driver to generate my latex output. 

I have installed and tested docutils, and run quicktest.py on a few snippets of
code, but as soon as I use markup using Python-specific roles such as :file:,
:ref:, :option:", or such I get an error. So I need a more comprehensive setup
that knows specifically about Python-specific (or sphinx-specific) markup.

I installed sphinx and ran it on Python docs sources, and I get the Latex OK.
So the know-how about Python "roles" and all that is there. If I could just
stop sphinx at the point where it has produced the parsing tree I'll be
happy. How do I do that?

I do not need handholding; I'm quite conversant with processing structured
documentation and making parsers and interpreters, but I'm ignorant of the way
things are configured for a custom Sphinx run. A pointer to relevant
documentation, a running example, the annotated setup of a project, or anything
that would allow me to capture the parsing tree would be of great help and save
me an enormous amount of time.

Thanks,
                                        Prof. Tommaso Toffoli

-- 
You received this message because you are subscribed to the Google Groups 
"sphinx-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sphinx-dev?hl=en.

Reply via email to