Escalating to python-dev for API design feedback is the usual path forward
if we reach an impasse in the tracker comments.

I'll make one more attempt at persuading Antoine here though: the fact that
we're being tempted to add "do not use this API the way you would normally
expect to use a Python API, even though it works exactly as you might
expect" to the docs is a big red flag for me :)

There's a split between the "low level API that exposes implementation
details" (the exception state triple) and "high level API that hides them"
in the current patch, and Antoine is entirely correct that we previously
omitted the latter. It doesn't follow for me that we should also hide the
fact that the higher level convenience API is implemented in terms of the
lower level more implementation oriented one.