Commit 6ef216cd authored by Raymond Hettinger's avatar Raymond Hettinger

Issue 27719: Remove a doc example that is not applicable in Python 3

parent 004a0c7f
...@@ -244,29 +244,7 @@ User-defined Exceptions ...@@ -244,29 +244,7 @@ User-defined Exceptions
Programs may name their own exceptions by creating a new exception class (see Programs may name their own exceptions by creating a new exception class (see
:ref:`tut-classes` for more about Python classes). Exceptions should typically :ref:`tut-classes` for more about Python classes). Exceptions should typically
be derived from the :exc:`Exception` class, either directly or indirectly. For be derived from the :exc:`Exception` class, either directly or indirectly.
example::
>>> class MyError(Exception):
... def __init__(self, value):
... self.value = value
... def __str__(self):
... return repr(self.value)
...
>>> try:
... raise MyError(2*2)
... except MyError as e:
... print('My exception occurred, value:', e.value)
...
My exception occurred, value: 4
>>> raise MyError('oops!')
Traceback (most recent call last):
File "<stdin>", line 1, in ?
__main__.MyError: 'oops!'
In this example, the default :meth:`__init__` of :class:`Exception` has been
overridden. The new behavior simply creates the *value* attribute. This
replaces the default behavior of creating the *args* attribute.
Exception classes can be defined which do anything any other class can do, but Exception classes can be defined which do anything any other class can do, but
are usually kept simple, often only offering a number of attributes that allow are usually kept simple, often only offering a number of attributes that allow
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment