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 orsenthil
Recipients abarry, belopolsky, berker.peksag, orsenthil, python-dev
Date 2016-01-11.15:27:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452526048.13.0.767538354342.issue26069@psf.upfronthosting.co.za>
In-reply-to
Content
Hi Berker, could you find the reference for it? It will be helpful to analyze.
IMO, the non-removal of 2.x-> 3.x APIs could be done on a case to case basis.

In this case, issue10371 made the change in (2010) of making the undocumented public methods to private internal and deprecated those old undocumented internal (but public) methods. It was a correct thing to do. Removal of the deprecated should have been done sooner. Otherwise, we are left with redundant methods (public and _private) in the same module serving no useful purpose.
History
Date User Action Args
2016-01-11 15:27:28orsenthilsetrecipients: + orsenthil, belopolsky, python-dev, berker.peksag, abarry
2016-01-11 15:27:28orsenthilsetmessageid: <1452526048.13.0.767538354342.issue26069@psf.upfronthosting.co.za>
2016-01-11 15:27:28orsenthillinkissue26069 messages
2016-01-11 15:27:27orsenthilcreate