> My assumption is, there is still in active interest in documenting our > deprecation policy, and it might be a good idea to move forward with a > pep PR?
+1 > I suspect that there is something in the devguide also I searched the devguide about deprecation policy, and it didn't turn up anything. Mariatta Wijaya On Sun, Apr 9, 2017 at 9:20 PM, Terry Reedy <tjre...@udel.edu> wrote: > On 4/9/2017 3:09 PM, Senthil Kumaran wrote: > >> I was looking for our Deprecation Policy and stumbled on this thread >> from January 2016. >> >> --------- >> >> PEP: XXX >> Title: Deprecation Policy >> Version: $Revision$ >> Last-Modified: $Date$ >> Author: Ezio Melotti <ezio.melotti at gmail.com> >> Status: Draft >> Type: Process >> Content-Type: text/x-rst >> Created: 29-Jan-2016 >> Post-History: >> >> https://mail.python.org/pipermail/python-committers/2016- >> January/003706.html >> >> I see that Ezio has already answered many questions in that thread, >> and perhaps a minor update to the proposal text is required. >> >> My assumption is, there is still in active interest in documenting our >> deprecation policy, and it might be a good idea to move forward with a >> pep PR? >> > > Yes. I suspect that there is something in the devguide also, but users as > well as contributors have an interest in the subject. > > tjr > > > _______________________________________________ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ >
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
