Victor Stinner ace47d7efd Issue #18408: PyEval_EvalFrameEx() and PyEval_CallObjectWithKeywords() now fail ...

with an assertion error if they are called with an exception set
(PyErr_Occurred()).

If these functions are called with an exception set, the exception may be
cleared and so the caller looses its exception.

Add also assertions to PyEval_CallObjectWithKeywords() and call_function() to
check if the function succeed with no exception set, or the function failed
with an exception set.

2013-07-18 01:41:08 +02:00

..

_iomodule.c

Describe 'surrogateescape' in the documentation.

2013-06-16 12:58:48 -04:00

_iomodule.h

If MS_WIN64 is defined, MS_WINDOWS is also defined: #ifdef can be simplified.

2013-06-25 00:37:25 +02:00

bufferedio.c

Issue #18408: PyEval_EvalFrameEx() and PyEval_CallObjectWithKeywords() now fail

2013-07-18 01:41:08 +02:00

bytesio.c

Merge 3.2.

2012-09-08 11:19:27 +02:00

fileio.c

Issue #18408: Fix fileio_read() on _PyBytes_Resize() failure

2013-07-16 21:36:02 +02:00

iobase.c

Merge 3.2, Issue #17047: remove doubled words found in 2.7 to 3.4

2013-03-11 17:45:12 -04:00

stringio.c

Issue #15841: The readable(), writable() and seekable() methods of BytesIO

2012-09-05 20:13:48 +02:00

textio.c

Issue #9566: _io: Use Py_SAFE_DOWNCAST for fix a compiler warning on Windows x64

2013-06-24 23:01:33 +02:00