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 fpom, r.david.murray, serhiy.storchaka
Date 2017-10-08.19:48:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507492097.57.0.213398074469.issue31726@psf.upfronthosting.co.za>
In-reply-to
Content
3.4 and 3.5 are in security maintenance mode only, and this is not a security bug.  This was fixed in master (3.7) as a result of issue 25324.  The decision there was made to not backport it because no one had complained about the problem previously.  Now we have a complaint, so perhaps that decision should be revisited?

There's also Serhiy's issue 30455.  I'm not sure if he's thinking about backporting that one or not.

And then there is the 2.7 question.  I'm not sure this is strong enough motivation to fix it there, though I wouldn't object (consistency is good).
History
Date User Action Args
2017-10-08 19:48:17r.david.murraysetrecipients: + r.david.murray, serhiy.storchaka, fpom
2017-10-08 19:48:17r.david.murraysetmessageid: <1507492097.57.0.213398074469.issue31726@psf.upfronthosting.co.za>
2017-10-08 19:48:17r.david.murraylinkissue31726 messages
2017-10-08 19:48:17r.david.murraycreate