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 bluebloodpole
Recipients bluebloodpole, georg.brandl
Date 2009-09-11.01:35:42
SpamBayes Score 4.0044778e-08
Marked as misclassified No
Message-id <1252632946.18.0.482571861035.issue6879@psf.upfronthosting.co.za>
In-reply-to
Content
v2.6.2 Python Tutorial
http://docs.python.org/tutorial/errors.html#raising-exceptions
Section 8. Errors and Exceptions
8.4. Raising Exceptions

It appears that in the example, the original may have been:
raise(NameError('HiThere')) and was then changed to
raise NameError('HiThere') but the explanation was not changed
accordingly.  The current state and my suggested change are found below,
respectively:

Currently:
"""
>>> raise NameError('HiThere')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
NameError: HiThere

The first argument to raise names the exception to be raised. The
optional second argument specifies the exception’s argument.
Alternatively, the above could be written as
raise NameError('HiThere'). Either form works fine, but there seems to
be a growing stylistic preference for the latter.
"""

Suggest change to:
"""
>>> raise NameError('HiThere')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
NameError: HiThere

The first argument to raise names the exception to be raised. The
optional second argument specifies the exception’s argument.
Alternatively, the above could be written as
raise(NameError('HiThere')). Either form works fine, but there seems to
be a growing stylistic preference for the former.
"""
History
Date User Action Args
2009-09-11 01:35:46bluebloodpolesetrecipients: + bluebloodpole, georg.brandl
2009-09-11 01:35:46bluebloodpolesetmessageid: <1252632946.18.0.482571861035.issue6879@psf.upfronthosting.co.za>
2009-09-11 01:35:44bluebloodpolelinkissue6879 messages
2009-09-11 01:35:43bluebloodpolecreate