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 Alexander Riccio
Recipients Alexander Riccio, eric.smith, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-10-22.06:27:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445495272.52.0.0250355401595.issue25386@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry for the delay: Gmail actually directed the update emails to my spam folder! Gmail said (something like): "It is in violation of Google's recommended email sender guidelines."

...and it's apparently not the first time this has happened with the python bugtracker: https://mail.python.org/pipermail/tracker-discuss/2015-January/003989.html


Anyways:

> That's a great test, thanks.

That IS a great test :)

> I'm curious: did you [Alexander] have some code where you're actually expecting an exception, or did you just stumble across this case?

Nope, I was just poking around the sources. I was curious to see what CPython's C implementation looked like, and decided to poke around some of the dustier, and the less used corners.

That, and I'm really OCD about checking return values.
History
Date User Action Args
2015-10-22 06:27:52Alexander Ricciosetrecipients: + Alexander Riccio, paul.moore, eric.smith, tim.golden, zach.ware, eryksun, steve.dower
2015-10-22 06:27:52Alexander Ricciosetmessageid: <1445495272.52.0.0250355401595.issue25386@psf.upfronthosting.co.za>
2015-10-22 06:27:52Alexander Ricciolinkissue25386 messages
2015-10-22 06:27:51Alexander Ricciocreate