Modules/pyexpat.c includes some archaic code to create temporary frames
so that, in even of an exception being raised, expat appears in the traceback.

The way this is implemented is a problem for three reasons:

1. It violates PEP 384.
2. It  is incorrect, see http://bugs.python.org/issue6359.
3. It is inefficient, as a frame is generated for each call, regardless of whether an exception is raised or not.

The attached patch fixes these issues.

Not sure how this can violate PEP 384, as it doesn't make it mandatory for builtin extensions to use the stable ABI.

The other concerns seem valid, although I don't like how the patch includes an unrelated change to ctypes.

W.r.t PEP 384:
Every module, except pyexpat, in the stdlib library treats frames as opaque objects, as PEP 384 requires.
(I'm exempting builtins and sys here)
I think it is unreasonable to expect authors of 3rd party modules to respect PEP 384 if the standard library does not.

W.r.t. the change to ctypes: I have simply moved a function from ctypes.c to traceback.c (and renamed it accordingly) so that pyexpat.c can access it.

FWIW, I think the patch's approach is ok. I just did a small comment on the review UI.

> I think it is unreasonable to expect authors of 3rd party modules to respect PEP 384 if the standard library does not.

I don't understand why you think that.  PEP 384 is intended to provide the means to maintain binary compatibility of extension modules so that they don't have to be recompiled for every minor version. Standard library extensions are recompiled for every Python release anyway.

Also, we don't expect authors to respect PEP 384. Either they choose to do so, and get the benefits, or they don't.

> I have simply moved a function from ctypes.c to traceback.c (and renamed it accordingly) so that pyexpat.c can access it.

I can see that. It would be cleaner to do the change in two steps, first move the utility function out from ctypes, then use it from pyexpat.  On the other hand we haven't been adamant about one-patch-one-change in the past.

Here is an updated patch with a test.

New changeset 5433ef907e4f by Antoine Pitrou in branch '3.4':
Issue #22462: Fix pyexpat's creation of a dummy frame to make it appear in exception tracebacks.
https://hg.python.org/cpython/rev/5433ef907e4f

New changeset f2f13aeb590a by Antoine Pitrou in branch 'default':
Issue #22462: Fix pyexpat's creation of a dummy frame to make it appear in exception tracebacks.
https://hg.python.org/cpython/rev/f2f13aeb590a

Patch pushed. I've kept the changes together :) Hopefully there won't be any ctypes regression.

according to  https://jenkins.qa.ubuntu.com/job/vivid-adt-python3.4/7/

test.test_pyexpat.HandlerExceptionTest now fails, but only when running in the installed location, not when running the tests from the builddir. any idea why?

New changeset e4b986350feb by Antoine Pitrou in branch '3.4':
Close issue #22895: fix test failure introduced by the fix for issue #22462.
https://hg.python.org/cpython/rev/e4b986350feb

New changeset 4990157343c6 by Antoine Pitrou in branch 'default':
Close issue #22895: fix test failure introduced by the fix for issue #22462.
https://hg.python.org/cpython/rev/4990157343c6

stage: patch review -> resolved

messages: + msg228774