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 gregory.p.smith
Recipients gregory.p.smith, michael.foord
Date 2014-01-08.09:29:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1389173381.83.0.641192416621.issue20165@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not comfortable changing this for 2.7 or 3.3 in case some code is unfortunately is depending on this behavior.  But as it is it does seem like the kind of thing that can hide problems (tests that are passing that are not expected to).

Here's a patch for 3.4 (minus the documentation update that'll need to explicitly mention this with a versionchanged::).
History
Date User Action Args
2014-01-08 09:29:41gregory.p.smithsetrecipients: + gregory.p.smith, michael.foord
2014-01-08 09:29:41gregory.p.smithsetmessageid: <1389173381.83.0.641192416621.issue20165@psf.upfronthosting.co.za>
2014-01-08 09:29:41gregory.p.smithlinkissue20165 messages
2014-01-08 09:29:41gregory.p.smithcreate