➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nedbat
Recipients ezio.melotti, loewis, nedbat
Date 2012-11-09.16:00:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352476827.06.0.580036202376.issue6359@psf.upfronthosting.co.za>
In-reply-to
Content 
I have no idea why pyexpat.c invokes the trace function in the first place.  Unless someone can explain why it does that when no other C extension does, my inclination would be to make it stop calling the trace function at all, not to fix how it calls it.
History
Date User Action Args
2012-11-09 16:00:27nedbatsetrecipients: + nedbat, loewis, ezio.melotti
2012-11-09 16:00:27nedbatsetmessageid: <1352476827.06.0.580036202376.issue6359@psf.upfronthosting.co.za>
2012-11-09 16:00:27nedbatlinkissue6359 messages
2012-11-09 16:00:26nedbatcreate