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 larry
Recipients larry, ncoghlan, pitrou, rbcollins
Date 2015-09-14.10:16:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442225779.86.0.208401775489.issue25108@psf.upfronthosting.co.za>
In-reply-to
Content
Tracebacks aren't my forte, but this does smell like a regression and something that should be fixed.

My worry about things like this is that it isn't as much a "bug" as a "badly implemented interface".  As in, that's the interface in 3.5, and people will depend on it, and we change it in a point release at our peril.  (That's why I didn't permit "fixing" warnings.warn(stacklevel=) for 3.4.)
History
Date User Action Args
2015-09-14 10:16:19larrysetrecipients: + larry, ncoghlan, pitrou, rbcollins
2015-09-14 10:16:19larrysetmessageid: <1442225779.86.0.208401775489.issue25108@psf.upfronthosting.co.za>
2015-09-14 10:16:19larrylinkissue25108 messages
2015-09-14 10:16:19larrycreate