blob: f465c5822c5ed9f140337f84f2280699c80457e0 [file] [log] [blame]
Georg Brandl116aa622007-08-15 14:28:22 +00001.. highlightlang:: c
2
3
4.. _exceptionhandling:
5
6******************
7Exception Handling
8******************
9
10The functions described in this chapter will let you handle and raise Python
11exceptions. It is important to understand some of the basics of Python
12exception handling. It works somewhat like the Unix :cdata:`errno` variable:
13there is a global indicator (per thread) of the last error that occurred. Most
14functions don't clear this on success, but will set it to indicate the cause of
15the error on failure. Most functions also return an error indicator, usually
16*NULL* if they are supposed to return a pointer, or ``-1`` if they return an
17integer (exception: the :cfunc:`PyArg_\*` functions return ``1`` for success and
18``0`` for failure).
19
20When a function must fail because some function it called failed, it generally
21doesn't set the error indicator; the function it called already set it. It is
22responsible for either handling the error and clearing the exception or
23returning after cleaning up any resources it holds (such as object references or
24memory allocations); it should *not* continue normally if it is not prepared to
25handle the error. If returning due to an error, it is important to indicate to
26the caller that an error has been set. If the error is not handled or carefully
27propagated, additional calls into the Python/C API may not behave as intended
28and may fail in mysterious ways.
29
30The error indicator consists of three Python objects corresponding to the result
31of ``sys.exc_info()``. API functions exist to interact with the error indicator
32in various ways. There is a separate error indicator for each thread.
33
Christian Heimes5b5e81c2007-12-31 16:14:33 +000034.. XXX Order of these should be more thoughtful.
35 Either alphabetical or some kind of structure.
Georg Brandl116aa622007-08-15 14:28:22 +000036
37
Georg Brandl115fb352009-02-05 10:56:37 +000038.. cfunction:: void PyErr_PrintEx(int set_sys_last_vars)
Georg Brandl116aa622007-08-15 14:28:22 +000039
40 Print a standard traceback to ``sys.stderr`` and clear the error indicator.
41 Call this function only when the error indicator is set. (Otherwise it will
42 cause a fatal error!)
43
Georg Brandl115fb352009-02-05 10:56:37 +000044 If *set_sys_last_vars* is nonzero, the variables :data:`sys.last_type`,
45 :data:`sys.last_value` and :data:`sys.last_traceback` will be set to the
46 type, value and traceback of the printed exception, respectively.
47
48
49.. cfunction:: void PyErr_Print()
50
51 Alias for ``PyErr_PrintEx(1)``.
52
Georg Brandl116aa622007-08-15 14:28:22 +000053
54.. cfunction:: PyObject* PyErr_Occurred()
55
56 Test whether the error indicator is set. If set, return the exception *type*
57 (the first argument to the last call to one of the :cfunc:`PyErr_Set\*`
58 functions or to :cfunc:`PyErr_Restore`). If not set, return *NULL*. You do not
59 own a reference to the return value, so you do not need to :cfunc:`Py_DECREF`
60 it.
61
62 .. note::
63
64 Do not compare the return value to a specific exception; use
65 :cfunc:`PyErr_ExceptionMatches` instead, shown below. (The comparison could
66 easily fail since the exception may be an instance instead of a class, in the
67 case of a class exception, or it may the a subclass of the expected exception.)
68
69
70.. cfunction:: int PyErr_ExceptionMatches(PyObject *exc)
71
72 Equivalent to ``PyErr_GivenExceptionMatches(PyErr_Occurred(), exc)``. This
73 should only be called when an exception is actually set; a memory access
74 violation will occur if no exception has been raised.
75
76
77.. cfunction:: int PyErr_GivenExceptionMatches(PyObject *given, PyObject *exc)
78
Benjamin Petersonda10d3b2009-01-01 00:23:30 +000079 Return true if the *given* exception matches the exception in *exc*. If
80 *exc* is a class object, this also returns true when *given* is an instance
81 of a subclass. If *exc* is a tuple, all exceptions in the tuple (and
82 recursively in subtuples) are searched for a match.
Georg Brandl116aa622007-08-15 14:28:22 +000083
84
85.. cfunction:: void PyErr_NormalizeException(PyObject**exc, PyObject**val, PyObject**tb)
86
87 Under certain circumstances, the values returned by :cfunc:`PyErr_Fetch` below
88 can be "unnormalized", meaning that ``*exc`` is a class object but ``*val`` is
89 not an instance of the same class. This function can be used to instantiate
90 the class in that case. If the values are already normalized, nothing happens.
91 The delayed normalization is implemented to improve performance.
92
93
94.. cfunction:: void PyErr_Clear()
95
96 Clear the error indicator. If the error indicator is not set, there is no
97 effect.
98
99
100.. cfunction:: void PyErr_Fetch(PyObject **ptype, PyObject **pvalue, PyObject **ptraceback)
101
102 Retrieve the error indicator into three variables whose addresses are passed.
103 If the error indicator is not set, set all three variables to *NULL*. If it is
104 set, it will be cleared and you own a reference to each object retrieved. The
105 value and traceback object may be *NULL* even when the type object is not.
106
107 .. note::
108
109 This function is normally only used by code that needs to handle exceptions or
110 by code that needs to save and restore the error indicator temporarily.
111
112
113.. cfunction:: void PyErr_Restore(PyObject *type, PyObject *value, PyObject *traceback)
114
115 Set the error indicator from the three objects. If the error indicator is
116 already set, it is cleared first. If the objects are *NULL*, the error
117 indicator is cleared. Do not pass a *NULL* type and non-*NULL* value or
118 traceback. The exception type should be a class. Do not pass an invalid
119 exception type or value. (Violating these rules will cause subtle problems
120 later.) This call takes away a reference to each object: you must own a
121 reference to each object before the call and after the call you no longer own
122 these references. (If you don't understand this, don't use this function. I
123 warned you.)
124
125 .. note::
126
127 This function is normally only used by code that needs to save and restore the
128 error indicator temporarily; use :cfunc:`PyErr_Fetch` to save the current
129 exception state.
130
131
132.. cfunction:: void PyErr_SetString(PyObject *type, const char *message)
133
134 This is the most common way to set the error indicator. The first argument
135 specifies the exception type; it is normally one of the standard exceptions,
136 e.g. :cdata:`PyExc_RuntimeError`. You need not increment its reference count.
137 The second argument is an error message; it is converted to a string object.
138
139
140.. cfunction:: void PyErr_SetObject(PyObject *type, PyObject *value)
141
142 This function is similar to :cfunc:`PyErr_SetString` but lets you specify an
143 arbitrary Python object for the "value" of the exception.
144
145
146.. cfunction:: PyObject* PyErr_Format(PyObject *exception, const char *format, ...)
147
Antoine Pitrouf66a1dd2010-11-27 21:01:19 +0000148 This function sets the error indicator and returns *NULL*. *exception*
149 should be a Python exception class. The *format* and subsequent
150 parameters help format the error message; they have the same meaning and
151 values as in :cfunc:`PyUnicode_FromFormat`.
Georg Brandl116aa622007-08-15 14:28:22 +0000152
153
154.. cfunction:: void PyErr_SetNone(PyObject *type)
155
156 This is a shorthand for ``PyErr_SetObject(type, Py_None)``.
157
158
159.. cfunction:: int PyErr_BadArgument()
160
161 This is a shorthand for ``PyErr_SetString(PyExc_TypeError, message)``, where
162 *message* indicates that a built-in operation was invoked with an illegal
163 argument. It is mostly for internal use.
164
165
166.. cfunction:: PyObject* PyErr_NoMemory()
167
168 This is a shorthand for ``PyErr_SetNone(PyExc_MemoryError)``; it returns *NULL*
169 so an object allocation function can write ``return PyErr_NoMemory();`` when it
170 runs out of memory.
171
172
173.. cfunction:: PyObject* PyErr_SetFromErrno(PyObject *type)
174
175 .. index:: single: strerror()
176
177 This is a convenience function to raise an exception when a C library function
178 has returned an error and set the C variable :cdata:`errno`. It constructs a
179 tuple object whose first item is the integer :cdata:`errno` value and whose
180 second item is the corresponding error message (gotten from :cfunc:`strerror`),
181 and then calls ``PyErr_SetObject(type, object)``. On Unix, when the
182 :cdata:`errno` value is :const:`EINTR`, indicating an interrupted system call,
183 this calls :cfunc:`PyErr_CheckSignals`, and if that set the error indicator,
184 leaves it set to that. The function always returns *NULL*, so a wrapper
185 function around a system call can write ``return PyErr_SetFromErrno(type);``
186 when the system call returns an error.
187
188
189.. cfunction:: PyObject* PyErr_SetFromErrnoWithFilename(PyObject *type, const char *filename)
190
191 Similar to :cfunc:`PyErr_SetFromErrno`, with the additional behavior that if
192 *filename* is not *NULL*, it is passed to the constructor of *type* as a third
193 parameter. In the case of exceptions such as :exc:`IOError` and :exc:`OSError`,
194 this is used to define the :attr:`filename` attribute of the exception instance.
195
196
197.. cfunction:: PyObject* PyErr_SetFromWindowsErr(int ierr)
198
199 This is a convenience function to raise :exc:`WindowsError`. If called with
200 *ierr* of :cdata:`0`, the error code returned by a call to :cfunc:`GetLastError`
201 is used instead. It calls the Win32 function :cfunc:`FormatMessage` to retrieve
202 the Windows description of error code given by *ierr* or :cfunc:`GetLastError`,
203 then it constructs a tuple object whose first item is the *ierr* value and whose
204 second item is the corresponding error message (gotten from
205 :cfunc:`FormatMessage`), and then calls ``PyErr_SetObject(PyExc_WindowsError,
206 object)``. This function always returns *NULL*. Availability: Windows.
207
208
209.. cfunction:: PyObject* PyErr_SetExcFromWindowsErr(PyObject *type, int ierr)
210
211 Similar to :cfunc:`PyErr_SetFromWindowsErr`, with an additional parameter
212 specifying the exception type to be raised. Availability: Windows.
213
Georg Brandl116aa622007-08-15 14:28:22 +0000214
215.. cfunction:: PyObject* PyErr_SetFromWindowsErrWithFilename(int ierr, const char *filename)
216
217 Similar to :cfunc:`PyErr_SetFromWindowsErr`, with the additional behavior that
218 if *filename* is not *NULL*, it is passed to the constructor of
219 :exc:`WindowsError` as a third parameter. Availability: Windows.
220
221
222.. cfunction:: PyObject* PyErr_SetExcFromWindowsErrWithFilename(PyObject *type, int ierr, char *filename)
223
224 Similar to :cfunc:`PyErr_SetFromWindowsErrWithFilename`, with an additional
225 parameter specifying the exception type to be raised. Availability: Windows.
226
Georg Brandl116aa622007-08-15 14:28:22 +0000227
228.. cfunction:: void PyErr_BadInternalCall()
229
Benjamin Peterson5c6d7872009-02-06 02:40:07 +0000230 This is a shorthand for ``PyErr_SetString(PyExc_SystemError, message)``,
231 where *message* indicates that an internal operation (e.g. a Python/C API
232 function) was invoked with an illegal argument. It is mostly for internal
233 use.
Georg Brandl116aa622007-08-15 14:28:22 +0000234
235
236.. cfunction:: int PyErr_WarnEx(PyObject *category, char *message, int stacklevel)
237
238 Issue a warning message. The *category* argument is a warning category (see
239 below) or *NULL*; the *message* argument is a message string. *stacklevel* is a
240 positive number giving a number of stack frames; the warning will be issued from
241 the currently executing line of code in that stack frame. A *stacklevel* of 1
242 is the function calling :cfunc:`PyErr_WarnEx`, 2 is the function above that,
243 and so forth.
244
245 This function normally prints a warning message to *sys.stderr*; however, it is
246 also possible that the user has specified that warnings are to be turned into
247 errors, and in that case this will raise an exception. It is also possible that
248 the function raises an exception because of a problem with the warning machinery
249 (the implementation imports the :mod:`warnings` module to do the heavy lifting).
250 The return value is ``0`` if no exception is raised, or ``-1`` if an exception
251 is raised. (It is not possible to determine whether a warning message is
252 actually printed, nor what the reason is for the exception; this is
253 intentional.) If an exception is raised, the caller should do its normal
254 exception handling (for example, :cfunc:`Py_DECREF` owned references and return
255 an error value).
256
257 Warning categories must be subclasses of :cdata:`Warning`; the default warning
258 category is :cdata:`RuntimeWarning`. The standard Python warning categories are
259 available as global variables whose names are ``PyExc_`` followed by the Python
260 exception name. These have the type :ctype:`PyObject\*`; they are all class
261 objects. Their names are :cdata:`PyExc_Warning`, :cdata:`PyExc_UserWarning`,
262 :cdata:`PyExc_UnicodeWarning`, :cdata:`PyExc_DeprecationWarning`,
263 :cdata:`PyExc_SyntaxWarning`, :cdata:`PyExc_RuntimeWarning`, and
264 :cdata:`PyExc_FutureWarning`. :cdata:`PyExc_Warning` is a subclass of
265 :cdata:`PyExc_Exception`; the other warning categories are subclasses of
266 :cdata:`PyExc_Warning`.
267
268 For information about warning control, see the documentation for the
269 :mod:`warnings` module and the :option:`-W` option in the command line
270 documentation. There is no C API for warning control.
271
272
273.. cfunction:: int PyErr_WarnExplicit(PyObject *category, const char *message, const char *filename, int lineno, const char *module, PyObject *registry)
274
275 Issue a warning message with explicit control over all warning attributes. This
276 is a straightforward wrapper around the Python function
277 :func:`warnings.warn_explicit`, see there for more information. The *module*
278 and *registry* arguments may be set to *NULL* to get the default effect
279 described there.
280
281
282.. cfunction:: int PyErr_CheckSignals()
283
284 .. index::
285 module: signal
286 single: SIGINT
287 single: KeyboardInterrupt (built-in exception)
288
289 This function interacts with Python's signal handling. It checks whether a
290 signal has been sent to the processes and if so, invokes the corresponding
291 signal handler. If the :mod:`signal` module is supported, this can invoke a
292 signal handler written in Python. In all cases, the default effect for
293 :const:`SIGINT` is to raise the :exc:`KeyboardInterrupt` exception. If an
294 exception is raised the error indicator is set and the function returns ``-1``;
295 otherwise the function returns ``0``. The error indicator may or may not be
296 cleared if it was previously set.
297
298
299.. cfunction:: void PyErr_SetInterrupt()
300
301 .. index::
302 single: SIGINT
303 single: KeyboardInterrupt (built-in exception)
304
305 This function simulates the effect of a :const:`SIGINT` signal arriving --- the
306 next time :cfunc:`PyErr_CheckSignals` is called, :exc:`KeyboardInterrupt` will
307 be raised. It may be called without holding the interpreter lock.
308
309 .. % XXX This was described as obsolete, but is used in
Georg Brandl2067bfd2008-05-25 13:05:15 +0000310 .. % _thread.interrupt_main() (used from IDLE), so it's still needed.
Georg Brandl116aa622007-08-15 14:28:22 +0000311
312
Christian Heimes5fb7c2a2007-12-24 08:52:31 +0000313.. cfunction:: int PySignal_SetWakeupFd(int fd)
314
315 This utility function specifies a file descriptor to which a ``'\0'`` byte will
316 be written whenever a signal is received. It returns the previous such file
317 descriptor. The value ``-1`` disables the feature; this is the initial state.
318 This is equivalent to :func:`signal.set_wakeup_fd` in Python, but without any
319 error checking. *fd* should be a valid file descriptor. The function should
320 only be called from the main thread.
321
322
Georg Brandl116aa622007-08-15 14:28:22 +0000323.. cfunction:: PyObject* PyErr_NewException(char *name, PyObject *base, PyObject *dict)
324
325 This utility function creates and returns a new exception object. The *name*
326 argument must be the name of the new exception, a C string of the form
327 ``module.class``. The *base* and *dict* arguments are normally *NULL*. This
328 creates a class object derived from :exc:`Exception` (accessible in C as
329 :cdata:`PyExc_Exception`).
330
331 The :attr:`__module__` attribute of the new class is set to the first part (up
332 to the last dot) of the *name* argument, and the class name is set to the last
333 part (after the last dot). The *base* argument can be used to specify alternate
334 base classes; it can either be only one class or a tuple of classes. The *dict*
335 argument can be used to specify a dictionary of class variables and methods.
336
337
338.. cfunction:: void PyErr_WriteUnraisable(PyObject *obj)
339
340 This utility function prints a warning message to ``sys.stderr`` when an
341 exception has been set but it is impossible for the interpreter to actually
342 raise the exception. It is used, for example, when an exception occurs in an
343 :meth:`__del__` method.
344
345 The function is called with a single argument *obj* that identifies the context
346 in which the unraisable exception occurred. The repr of *obj* will be printed in
347 the warning message.
348
349
Georg Brandlab6f2f62009-03-31 04:16:10 +0000350Exception Objects
351=================
352
353.. cfunction:: PyObject* PyException_GetTraceback(PyObject *ex)
354
355 Return the traceback associated with the exception as a new reference, as
356 accessible from Python through :attr:`__traceback__`. If there is no
357 traceback associated, this returns *NULL*.
358
359
360.. cfunction:: int PyException_SetTraceback(PyObject *ex, PyObject *tb)
361
362 Set the traceback associated with the exception to *tb*. Use ``Py_None`` to
363 clear it.
364
365
366.. cfunction:: PyObject* PyException_GetContext(PyObject *ex)
367
368 Return the context (another exception instance during whose handling *ex* was
369 raised) associated with the exception as a new reference, as accessible from
370 Python through :attr:`__context__`. If there is no context associated, this
371 returns *NULL*.
372
373
374.. cfunction:: void PyException_SetContext(PyObject *ex, PyObject *ctx)
375
376 Set the context associated with the exception to *ctx*. Use *NULL* to clear
377 it. There is no type check to make sure that *ctx* is an exception instance.
378 This steals a reference to *ctx*.
379
380
381.. cfunction:: PyObject* PyException_GetCause(PyObject *ex)
382
383 Return the cause (another exception instance set by ``raise ... from ...``)
384 associated with the exception as a new reference, as accessible from Python
385 through :attr:`__cause__`. If there is no cause associated, this returns
386 *NULL*.
387
388
389.. cfunction:: void PyException_SetCause(PyObject *ex, PyObject *ctx)
390
391 Set the cause associated with the exception to *ctx*. Use *NULL* to clear
392 it. There is no type check to make sure that *ctx* is an exception instance.
393 This steals a reference to *ctx*.
394
395
Georg Brandlf65e25b2010-11-26 09:05:43 +0000396.. _unicodeexceptions:
397
398Unicode Exception Objects
399=========================
400
401The following functions are used to create and modify Unicode exceptions from C.
402
403.. cfunction:: PyObject* PyUnicodeDecodeError_Create(const char *encoding, const char *object, Py_ssize_t length, Py_ssize_t start, Py_ssize_t end, const char *reason)
404
405 Create a :class:`UnicodeDecodeError` object with the attributes *encoding*,
406 *object*, *length*, *start*, *end* and *reason*.
407
408.. cfunction:: PyObject* PyUnicodeEncodeError_Create(const char *encoding, const Py_UNICODE *object, Py_ssize_t length, Py_ssize_t start, Py_ssize_t end, const char *reason)
409
410 Create a :class:`UnicodeEncodeError` object with the attributes *encoding*,
411 *object*, *length*, *start*, *end* and *reason*.
412
413.. cfunction:: PyObject* PyUnicodeTranslateError_Create(const Py_UNICODE *object, Py_ssize_t length, Py_ssize_t start, Py_ssize_t end, const char *reason)
414
415 Create a :class:`UnicodeTranslateError` object with the attributes *object*,
416 *length*, *start*, *end* and *reason*.
417
418.. cfunction:: PyObject* PyUnicodeDecodeError_GetEncoding(PyObject *exc)
419 PyObject* PyUnicodeEncodeError_GetEncoding(PyObject *exc)
420
421 Return the *encoding* attribute of the given exception object.
422
423.. cfunction:: PyObject* PyUnicodeDecodeError_GetObject(PyObject *exc)
424 PyObject* PyUnicodeEncodeError_GetObject(PyObject *exc)
425 PyObject* PyUnicodeTranslateError_GetObject(PyObject *exc)
426
427 Return the *object* attribute of the given exception object.
428
429.. cfunction:: int PyUnicodeDecodeError_GetStart(PyObject *exc, Py_ssize_t *start)
430 int PyUnicodeEncodeError_GetStart(PyObject *exc, Py_ssize_t *start)
431 int PyUnicodeTranslateError_GetStart(PyObject *exc, Py_ssize_t *start)
432
433 Get the *start* attribute of the given exception object and place it into
434 *\*start*. *start* must not be *NULL*. Return ``0`` on success, ``-1`` on
435 failure.
436
437.. cfunction:: int PyUnicodeDecodeError_SetStart(PyObject *exc, Py_ssize_t start)
438 int PyUnicodeEncodeError_SetStart(PyObject *exc, Py_ssize_t start)
439 int PyUnicodeTranslateError_SetStart(PyObject *exc, Py_ssize_t start)
440
441 Set the *start* attribute of the given exception object to *start*. Return
442 ``0`` on success, ``-1`` on failure.
443
444.. cfunction:: int PyUnicodeDecodeError_GetEnd(PyObject *exc, Py_ssize_t *end)
445 int PyUnicodeEncodeError_GetEnd(PyObject *exc, Py_ssize_t *end)
446 int PyUnicodeTranslateError_GetEnd(PyObject *exc, Py_ssize_t *end)
447
448 Get the *end* attribute of the given exception object and place it into
449 *\*end*. *end* must not be *NULL*. Return ``0`` on success, ``-1`` on
450 failure.
451
452.. cfunction:: int PyUnicodeDecodeError_SetEnd(PyObject *exc, Py_ssize_t end)
453 int PyUnicodeEncodeError_SetEnd(PyObject *exc, Py_ssize_t end)
454 int PyUnicodeTranslateError_SetEnd(PyObject *exc, Py_ssize_t end)
455
456 Set the *end* attribute of the given exception object to *end*. Return ``0``
457 on success, ``-1`` on failure.
458
459.. cfunction:: PyObject* PyUnicodeDecodeError_GetReason(PyObject *exc)
460 PyObject* PyUnicodeEncodeError_GetReason(PyObject *exc)
461 PyObject* PyUnicodeTranslateError_GetReason(PyObject *exc)
462
463 Return the *reason* attribute of the given exception object.
464
465.. cfunction:: int PyUnicodeDecodeError_SetReason(PyObject *exc, const char *reason)
466 int PyUnicodeEncodeError_SetReason(PyObject *exc, const char *reason)
467 int PyUnicodeTranslateError_SetReason(PyObject *exc, const char *reason)
468
469 Set the *reason* attribute of the given exception object to *reason*. Return
470 ``0`` on success, ``-1`` on failure.
471
472
Georg Brandl16215c72010-10-06 07:59:52 +0000473Recursion Control
474=================
475
476These two functions provide a way to perform safe recursive calls at the C
477level, both in the core and in extension modules. They are needed if the
478recursive code does not necessarily invoke Python code (which tracks its
479recursion depth automatically).
480
481.. cfunction:: int Py_EnterRecursiveCall(char *where)
482
483 Marks a point where a recursive C-level call is about to be performed.
484
485 If :const:`USE_STACKCHECK` is defined, this function checks if the the OS
486 stack overflowed using :cfunc:`PyOS_CheckStack`. In this is the case, it
487 sets a :exc:`MemoryError` and returns a nonzero value.
488
489 The function then checks if the recursion limit is reached. If this is the
490 case, a :exc:`RuntimeError` is set and a nonzero value is returned.
491 Otherwise, zero is returned.
492
493 *where* should be a string such as ``" in instance check"`` to be
494 concatenated to the :exc:`RuntimeError` message caused by the recursion depth
495 limit.
496
497.. cfunction:: void Py_LeaveRecursiveCall()
498
499 Ends a :cfunc:`Py_EnterRecursiveCall`. Must be called once for each
500 *successful* invocation of :cfunc:`Py_EnterRecursiveCall`.
501
502
Georg Brandl116aa622007-08-15 14:28:22 +0000503.. _standardexceptions:
504
505Standard Exceptions
506===================
507
508All standard Python exceptions are available as global variables whose names are
509``PyExc_`` followed by the Python exception name. These have the type
510:ctype:`PyObject\*`; they are all class objects. For completeness, here are all
511the variables:
512
513+------------------------------------+----------------------------+----------+
514| C Name | Python Name | Notes |
515+====================================+============================+==========+
Georg Brandl321976b2007-09-01 12:33:24 +0000516| :cdata:`PyExc_BaseException` | :exc:`BaseException` | \(1) |
Georg Brandl116aa622007-08-15 14:28:22 +0000517+------------------------------------+----------------------------+----------+
518| :cdata:`PyExc_Exception` | :exc:`Exception` | \(1) |
519+------------------------------------+----------------------------+----------+
520| :cdata:`PyExc_ArithmeticError` | :exc:`ArithmeticError` | \(1) |
521+------------------------------------+----------------------------+----------+
522| :cdata:`PyExc_LookupError` | :exc:`LookupError` | \(1) |
523+------------------------------------+----------------------------+----------+
524| :cdata:`PyExc_AssertionError` | :exc:`AssertionError` | |
525+------------------------------------+----------------------------+----------+
526| :cdata:`PyExc_AttributeError` | :exc:`AttributeError` | |
527+------------------------------------+----------------------------+----------+
528| :cdata:`PyExc_EOFError` | :exc:`EOFError` | |
529+------------------------------------+----------------------------+----------+
530| :cdata:`PyExc_EnvironmentError` | :exc:`EnvironmentError` | \(1) |
531+------------------------------------+----------------------------+----------+
532| :cdata:`PyExc_FloatingPointError` | :exc:`FloatingPointError` | |
533+------------------------------------+----------------------------+----------+
534| :cdata:`PyExc_IOError` | :exc:`IOError` | |
535+------------------------------------+----------------------------+----------+
536| :cdata:`PyExc_ImportError` | :exc:`ImportError` | |
537+------------------------------------+----------------------------+----------+
538| :cdata:`PyExc_IndexError` | :exc:`IndexError` | |
539+------------------------------------+----------------------------+----------+
540| :cdata:`PyExc_KeyError` | :exc:`KeyError` | |
541+------------------------------------+----------------------------+----------+
542| :cdata:`PyExc_KeyboardInterrupt` | :exc:`KeyboardInterrupt` | |
543+------------------------------------+----------------------------+----------+
544| :cdata:`PyExc_MemoryError` | :exc:`MemoryError` | |
545+------------------------------------+----------------------------+----------+
546| :cdata:`PyExc_NameError` | :exc:`NameError` | |
547+------------------------------------+----------------------------+----------+
548| :cdata:`PyExc_NotImplementedError` | :exc:`NotImplementedError` | |
549+------------------------------------+----------------------------+----------+
550| :cdata:`PyExc_OSError` | :exc:`OSError` | |
551+------------------------------------+----------------------------+----------+
552| :cdata:`PyExc_OverflowError` | :exc:`OverflowError` | |
553+------------------------------------+----------------------------+----------+
554| :cdata:`PyExc_ReferenceError` | :exc:`ReferenceError` | \(2) |
555+------------------------------------+----------------------------+----------+
556| :cdata:`PyExc_RuntimeError` | :exc:`RuntimeError` | |
557+------------------------------------+----------------------------+----------+
558| :cdata:`PyExc_SyntaxError` | :exc:`SyntaxError` | |
559+------------------------------------+----------------------------+----------+
560| :cdata:`PyExc_SystemError` | :exc:`SystemError` | |
561+------------------------------------+----------------------------+----------+
562| :cdata:`PyExc_SystemExit` | :exc:`SystemExit` | |
563+------------------------------------+----------------------------+----------+
564| :cdata:`PyExc_TypeError` | :exc:`TypeError` | |
565+------------------------------------+----------------------------+----------+
566| :cdata:`PyExc_ValueError` | :exc:`ValueError` | |
567+------------------------------------+----------------------------+----------+
568| :cdata:`PyExc_WindowsError` | :exc:`WindowsError` | \(3) |
569+------------------------------------+----------------------------+----------+
570| :cdata:`PyExc_ZeroDivisionError` | :exc:`ZeroDivisionError` | |
571+------------------------------------+----------------------------+----------+
572
573.. index::
574 single: PyExc_BaseException
575 single: PyExc_Exception
576 single: PyExc_ArithmeticError
577 single: PyExc_LookupError
578 single: PyExc_AssertionError
579 single: PyExc_AttributeError
580 single: PyExc_EOFError
581 single: PyExc_EnvironmentError
582 single: PyExc_FloatingPointError
583 single: PyExc_IOError
584 single: PyExc_ImportError
585 single: PyExc_IndexError
586 single: PyExc_KeyError
587 single: PyExc_KeyboardInterrupt
588 single: PyExc_MemoryError
589 single: PyExc_NameError
590 single: PyExc_NotImplementedError
591 single: PyExc_OSError
592 single: PyExc_OverflowError
593 single: PyExc_ReferenceError
594 single: PyExc_RuntimeError
595 single: PyExc_SyntaxError
596 single: PyExc_SystemError
597 single: PyExc_SystemExit
598 single: PyExc_TypeError
599 single: PyExc_ValueError
600 single: PyExc_WindowsError
601 single: PyExc_ZeroDivisionError
602
603Notes:
604
605(1)
606 This is a base class for other standard exceptions.
607
608(2)
609 This is the same as :exc:`weakref.ReferenceError`.
610
611(3)
612 Only defined on Windows; protect code that uses this by testing that the
613 preprocessor macro ``MS_WINDOWS`` is defined.