➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients docs@python, eric.araujo, ncoghlan
Date 2014-07-27.01:53:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1406426038.28.0.587569584121.issue22014@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2014-07-27 01:53:58ncoghlansetrecipients: + ncoghlan, eric.araujo, docs@python
2014-07-27 01:53:58ncoghlansetmessageid: <1406426038.28.0.587569584121.issue22014@psf.upfronthosting.co.za>
2014-07-27 01:53:58ncoghlanlinkissue22014 messages
2014-07-27 01:53:57ncoghlancreate