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 alex, barry, eric.araujo, gvanrossum, ncoghlan, pitrou, r.david.murray
Date 2017-11-09.02:19:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It was never about putting the interests of the app developers first, it was about putting the interests of the users first: not being pestered by seeing deprecation warnings they can't do anything about.

So yeah, maybe a PEP explaining the logic would be helpful, since there seems to be disagreement about what the logic is.  I'm not in a position to write it, though.

Maybe it would indeed be worth it to push this change into Fedora/RedHat and see what the response is before doing it in core?  Kind of the same principle as putting something on pypi before putting in the stdlib.

Also note that *no matter what you do* adding keywords is painful.  That's why we try really really hard not to do it.
Date User Action Args
2017-11-09 02:19:21r.david.murraysetrecipients: + r.david.murray, gvanrossum, barry, ncoghlan, pitrou, eric.araujo, alex
2017-11-09 02:19:21r.david.murraysetmessageid: <>
2017-11-09 02:19:21r.david.murraylinkissue31975 messages
2017-11-09 02:19:20r.david.murraycreate