Barry A. Warsaw <> added the comment:

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 


Python tracker <>
Python-bugs-list mailing list

Reply via email to