Nick Coghlan added the comment:
Oh, nice - the "start-after" and "end-before" options look like they might be
the way to go.
If I'm reading the docs right, a block like the following would include the
OSError section of the tree:
.. literalinclude exceptions.txt
:start-after: OSError
:end-before: ReferenceError
:prepend:
I think that's really the section that could most benefit from showing the
structure inline.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22014>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
