Re: [python-committers] Deprecation Policy PEP

2016-01-30 Thread Terry Reedy
On 1/30/2016 3:39 AM, Nick Coghlan wrote: Me too, but only if you add a PendingDeprecationWarning to PendingDeprecationWarning . There were some discussions a while back of restoring a distinction between the two by having code executed directly at the REPL (whether at the command line or in I

Re: [python-committers] Deprecation Policy PEP

2016-01-30 Thread Nick Coghlan
On 30 January 2016 at 13:28, Martin Panter wrote: > On 29 January 2016 at 21:59, Serhiy Storchaka wrote: >> On 29.01.16 21:56, Ezio Melotti wrote: >>> On Fri, Jan 29, 2016 at 8:00 PM, Serhiy Storchaka >>> wrote: Some deprecation can be documentation-only. >>> >>> Do you have examples where

Re: [python-committers] Deprecation Policy PEP

2016-01-30 Thread Nick Coghlan
On 30 January 2016 at 09:39, Barry Warsaw wrote: > On Jan 29, 2016, at 06:11 PM, Brett Cannon wrote: > >>+1 from me as well, especially once Serhiy's comments are addressed. Likewise - an additional proofreading pass would be useful, but the overall content looks fine to me. > Me too, but only i