From aec0127720b72884f87329396c6a31e4a02ce7ad Mon Sep 17 00:00:00 2001 From: Benjamin Peterson Date: Mon, 10 May 2010 20:52:35 +0000 Subject: [PATCH] Merged revisions 81057 via svnmerge from svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r81057 | benjamin.peterson | 2010-05-10 15:49:20 -0500 (Mon, 10 May 2010) | 1 line remove reference to second argument to raise #8676 ........ --- Doc/library/exceptions.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Doc/library/exceptions.rst b/Doc/library/exceptions.rst index 17a0fed8cb..fb3ae94d41 100644 --- a/Doc/library/exceptions.rst +++ b/Doc/library/exceptions.rst @@ -28,10 +28,10 @@ The built-in exceptions listed below can be generated by the interpreter or built-in functions. Except where mentioned, they have an "associated value" indicating the detailed cause of the error. This may be a string or a tuple containing several items of information (e.g., an error code and a string -explaining the code). The associated value is the second argument to the -:keyword:`raise` statement. If the exception class is derived from the standard -root class :exc:`BaseException`, the associated value is present as the -exception instance's :attr:`args` attribute. +explaining the code). The associated value is usually passed to the exception +class's constructor. If the exception class is derived from the standard root +class :exc:`BaseException`, the associated value is present as the exception +instance's :attr:`args` attribute. User code can raise built-in exceptions. This can be used to test an exception handler or to report an error condition "just like" the situation in which the -- 2.40.0