Senthil Kumaran added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26069> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
