cpython/Modules/_io
Victor Stinner 4a7cc88472 Issue #23571: PyObject_Call(), PyCFunction_Call() and call_function() now
raise a SystemError if a function returns a result and raises an exception.
The SystemError is chained to the previous exception.

Refactor also PyObject_Call() and PyCFunction_Call() to make them more readable.

Remove some checks which became useless (duplicate checks).

Change reviewed by Serhiy Storchaka.
2015-03-06 23:35:27 +01:00
..
_iomodule.c Issue #21715: Extracted shared complicated code in the _io module to new 2014-10-08 22:32:50 +03:00
_iomodule.h Issue #22883: Got rid of outdated references to PyInt and PyString in comments. 2015-02-17 10:14:30 +02:00
bufferedio.c Issue #23571: PyObject_Call(), PyCFunction_Call() and call_function() now 2015-03-06 23:35:27 +01:00
bytesio.c Issue #14203: Remove obsolete support for view==NULL in bytesiobuf_getbuffer() 2015-02-03 21:43:23 +01:00
fileio.c Issue #23524: Replace _PyVerify_fd function with calling _set_thread_local_invalid_parameter_handler on every thread. 2015-03-06 14:47:02 -08:00
iobase.c #15840: make docs consistent by saying operations on closed files raise ValueError. 2014-04-15 21:11:36 -04:00
stringio.c Issue #15841: The readable(), writable() and seekable() methods of BytesIO 2012-09-05 20:13:48 +02:00
textio.c merge 3.4 (#23093) 2014-12-21 21:00:51 -06:00