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.

Title: Slight inconsistency in documentation appearances of RuntimeError
Type: Stage:
Components: Documentation Versions: Python 3.0, Python 3.1
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: MLModel, benjamin.peterson, georg.brandl
Priority: normal Keywords:

Created on 2009-02-16 14:46 by MLModel, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg82241 - (view) Author: Mitchell Model (MLModel) Date: 2009-02-16 14:46
The Library Exceptions documentation describes RuntimeException as "mostly 
a relic from a previous version of the interpreter; it is not used very 
much any more." Yet, the Reference in describing the raise statement uses 
RuntimeException as an example:

raise RuntimeError("foo occurred").with_traceback(tracebackobj)

This seems slightly misleading. It might be better to just use Exception 
as the example there.
msg82246 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2009-02-16 16:15
Fixed in r69675.
Date User Action Args
2022-04-11 14:56:45adminsetgithub: 49531
2009-02-16 16:15:53benjamin.petersonsetstatus: open -> closed
nosy: + benjamin.peterson
resolution: fixed
messages: + msg82246
2009-02-16 14:46:35MLModelcreate