diff Doc/api/exceptions.tex @ 29302:08a1cbdd0367 legacy-trunk

SF bug #719367, string exceptions are deprecated Remove references to string based exceptions in the doc.
author Neal Norwitz <nnorwitz@gmail.com>
date Thu, 29 May 2003 02:17:23 +0000
parents 732836666000
children 381ae326ee65
line wrap: on
line diff
--- a/Doc/api/exceptions.tex	Thu May 29 02:10:31 2003 +0000
+++ b/Doc/api/exceptions.tex	Thu May 29 02:17:23 2003 +0000
@@ -102,7 +102,7 @@
   indicator is already set, it is cleared first.  If the objects are
   \NULL, the error indicator is cleared.  Do not pass a \NULL{} type
   and non-\NULL{} value or traceback.  The exception type should be a
-  string or class.  Do not pass an invalid exception type or value.
+  class.  Do not pass an invalid exception type or value.
   (Violating these rules will cause subtle problems later.)  This call
   takes away a reference to each object: you must own a reference to
   each object before the call and after the call you no longer own
@@ -130,7 +130,7 @@
 \begin{cfuncdesc}{PyObject*}{PyErr_Format}{PyObject *exception,
                                            const char *format, \moreargs}
   This function sets the error indicator and returns \NULL.
-  \var{exception} should be a Python exception (string or class, not
+  \var{exception} should be a Python exception (class, not
   an instance).  \var{format} should be a string, containing format
   codes, similar to \cfunction{printf()}. The \code{width.precision}
   before a format code is parsed, but the width part is ignored.