[python-committers] Deprecation Policy PEP Thread
Terry Reedy
tjreedy at udel.edu
Sun Apr 9 15:20:07 EDT 2017
More information about the python-committers mailing list
Sun Apr 9 15:20:07 EDT 2017
- Previous message (by thread): [python-committers] Deprecation Policy PEP Thread
- Next message (by thread): [python-committers] Deprecation Policy PEP Thread
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): [python-committers] Deprecation Policy PEP Thread
- Next message (by thread): [python-committers] Deprecation Policy PEP Thread
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list