➜

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 PaulRudin, chillaranand, docs@python, eric.snow, r.david.murray, s7v7nislands@gmail.com, terry.reedy
Date 2018-01-04.14:09:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515074973.3.0.467229070634.issue17972@psf.upfronthosting.co.za>
In-reply-to
Content 
I think adding an __all__ in 3.7 would be reasonable.  You are right that we can't simply rename them for backward compatibility reasons.  We could rename them, and leave a stub function (that calls the renamed function) but issues a deprecation warning.  We've done that for other old internal APIs that we wanted to mark as private elsewhere in the stdlib.  The question is, is it worth the trouble to do it?
History
Date User Action Args
2018-01-04 14:09:33r.david.murraysetrecipients: + r.david.murray, terry.reedy, docs@python, eric.snow, s7v7nislands@gmail.com, chillaranand, PaulRudin
2018-01-04 14:09:33r.david.murraysetmessageid: <1515074973.3.0.467229070634.issue17972@psf.upfronthosting.co.za>
2018-01-04 14:09:33r.david.murraylinkissue17972 messages
2018-01-04 14:09:33r.david.murraycreate