Hi,
firstly, thanks for Sphinx, it's shaping up nicely!
Rewriting a .tex document, I'd like to refer to a figure that can differ
for various configurations (the original used \opt).
Initially I wrote something like:
See :ref:`status`
.. ifconfig:: releaselevel == 'alpha'
.. _
Hi everyone. I'm attempting to document a fairly large python project
of which a major component is an extensive C++ library we've wrapped
with Boost.Python. I'm using autodoc and everything is working great
- in fact I've written a simple Sphinx extension using the new autodoc
events that clean
Hi,
Tue, 19 May 2009 20:12:38 -0700, Matthew Turk kirjoitti:
[clip]
> identically to how the autodoc extension would work -- rather than
> autodocing the underlying class itself, which is not meant to be
> accessed directly. Is there a way to supply an override to the
> displayed name (in additi
On May 19, 2009, at 11:12 PM, Matthew Turk wrote:
>
> Hi there,
>
> Just as an upfront, I'm loving using sphinx to document a project.
> I'm writing because I'm stuck at a particular usage pattern we have in
> our code, and how to properly document it. We have objects that have
> affiliated "de
