➜

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 barry
Recipients barry, brett.cannon, eric.snow, ncoghlan, pitrou, pmpp, rhettinger
Date 2018-04-22.17:00:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1524416415.61.0.682650639539.issue33277@psf.upfronthosting.co.za>
In-reply-to
Content 
Not that I've thought this through in much detail, but what if we start out by proxying those module attributes to the spec via PEP 562 hooks?  We can do that in 3.8, issue (silent?) deprecation warnings, and then do a full deprecation process for those module attributes?

It's not a terrible thing to keep those attributes as long as they match what's in the spec.  It's a problem when they're out of sync (see bpo-32305 and bpo-32303).
History
Date User Action Args
2018-04-22 17:00:15barrysetrecipients: + barry, brett.cannon, rhettinger, ncoghlan, pitrou, pmpp, eric.snow
2018-04-22 17:00:15barrysetmessageid: <1524416415.61.0.682650639539.issue33277@psf.upfronthosting.co.za>
2018-04-22 17:00:15barrylinkissue33277 messages
2018-04-22 17:00:15barrycreate