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 vstinner
Recipients christian.heimes, giampaolo.rodola, gregory.p.smith, izbyshev, jwilk, serhiy.storchaka, vstinner
Date 2019-04-18.12:54:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555592053.37.0.381995398849.issue35755@roundup.psfhosted.org>
In-reply-to
Content
> For Python 2.7... well, I don't think that this issue is important enough to justify a backport. I prefer to do nothing rather than having to deal with unhappy users complaining that Python 2.7 changed broke their application in a minor 2.7.x release :-) Even if, again, the risk of regression is very low.

Same rationale for Python 3.6. While I would call this change related to security, I'm not comfortable to backport the change. The issue is not important enough compared to the risk of regression.
History
Date User Action Args
2019-04-18 12:54:13vstinnersetrecipients: + vstinner, gregory.p.smith, giampaolo.rodola, christian.heimes, jwilk, serhiy.storchaka, izbyshev
2019-04-18 12:54:13vstinnersetmessageid: <1555592053.37.0.381995398849.issue35755@roundup.psfhosted.org>
2019-04-18 12:54:13vstinnerlinkissue35755 messages
2019-04-18 12:54:13vstinnercreate