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 r.david.murray
Recipients martin.panter, r.david.murray, rhettinger, serhiy.storchaka
Date 2015-05-26.14:43:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432651400.38.0.732865670264.issue24284@psf.upfronthosting.co.za>
In-reply-to
Content
Just in the what's new porting section, I think.  The fact that there "should" be very little to no code that relies on this is why I'd like to see it fixed.  The fact that the report was a theoretical one, and not one that broke code, is why I think we should fix it only in 3.5.
History
Date User Action Args
2015-05-26 14:43:20r.david.murraysetrecipients: + r.david.murray, rhettinger, martin.panter, serhiy.storchaka
2015-05-26 14:43:20r.david.murraysetmessageid: <1432651400.38.0.732865670264.issue24284@psf.upfronthosting.co.za>
2015-05-26 14:43:20r.david.murraylinkissue24284 messages
2015-05-26 14:43:20r.david.murraycreate