After more tests, I now think that it is the safest option.

for TYPE_DICT and stop immedialty on first r_object() failure

TYPE_SMALL_TUPLE

failure, don't read any more data

_ctypes_alloc_format_string() failure

failure

failure

Don't call PyObject_CallObject() with NULL parameters and an exception set.

call a Python function with an exception set

with an exception set

It affects docs of 3.3 in a way that was fixed differently in 3.4

In 3.3 iterparse accepts a tuple in events (the C accelerator enforces this).
This limitation was lifted in Python 3.4

exception set

asyncio: Add support for running subprocesses on Windows with the IOCP event loop (Richard Oudkerk).

The bug was introduced with the select.epoll module! So it's 5 years old :-)

memcmp() just takes raw pointers