[issue22014] Add summary table for OS exception <-> errno mapping

[Jon Poler]

Jon Poler added the comment:

I will give this a shot if it is just hard-coding a table with errno names. 
Dynamically scraping the errno names and inserting them with the exception 
hierarchy might be beyond me since I've never used Sphinx before.

--
nosy: +jon.poler

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22014] Add summary table for OS exception <-> errno mapping

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti
stage:  -> needs patch
type:  -> enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22014] Add summary table for OS exception <-> errno mapping

[Nick Coghlan]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22014] Add summary table for OS exception <-> errno mapping

[Éric Araujo]

Éric Araujo added the comment:

literalinclude lets you select only some lines of the file: 
http://sphinx-doc.org/markup/code.html#includes

--
nosy: +eric.araujo

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22014] Add summary table for OS exception <-> errno mapping

[Nick Coghlan]

Nick Coghlan added the comment:

Another idea would be to include fragments of the ASCII art hierarchy 
throughout the doc, but that's trickier than it sounds, since we just use 
literalinclude to generate the current one.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue22014] Add summary table for OS exception <-> errno mapping

[Nick Coghlan]

New submission from Nick Coghlan:

It would be handy if the main OS exception docs at 
https://docs.python.org/3/library/exceptions.html#os-exceptions included a 
summary table mapping between exception types and errno names, akin to the one 
in the original PEP 
(http://www.python.org/dev/peps/pep-3151/#new-exception-classes)

--
assignee: docs@python
components: Documentation
keywords: easy
messages: 223499
nosy: docs@python, ncoghlan
priority: normal
severity: normal
status: open
title: Add summary table for OS exception <-> errno mapping
versions: Python 3.4, Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com