Re: [python-committers] Enabling depreciation warnings feature code cutoff

On Mon, 06 Nov 2017 13:25:09 -0600, Neil Schemenauer wrote: > On 2017-11-06, R. David Murray wrote: > > I'm curious which ones you are seeing it in? It could be we are > > operating in different problem spaces :) > > In the last few months: Pillow, docutils, dateutil.

Re: [python-committers] Enabling depreciation warnings feature code cutoff

On 2017-11-06, R. David Murray wrote: > I'm curious which ones you are seeing it in? It could be we are > operating in different problem spaces :) In the last few months: Pillow, docutils, dateutil. Some of them could have been PendingDeprecationWarning, I'm not sure. I had that enabled as

Re: [python-committers] Enabling depreciation warnings feature code cutoff

On Mon, 06 Nov 2017 12:51:45 -0600, Neil Schemenauer wrote: > Another idea is to have venv to turn them on by default or, based on > a command-line option, do it. Or, maybe the unit testing frameworks > should turn on the warnings when they run. Unit test frameworks,

Re: [python-committers] Enabling depreciation warnings feature code cutoff

I also feel this decision was a mistake. If there's a consensus to revert, I'm happy to draft a PEP. Alex On Nov 6, 2017 1:58 PM, "Neil Schemenauer" wrote: > On 2017-11-06, Nick Coghlan wrote: > > Gah, seven years on from Python 2.7's release, I still get caught by > >

Re: [python-committers] [Python-Dev] Reminder: 12 weeks to 3.7 feature code cutoff

On Mon, 06 Nov 2017 11:46:48 +1000, Nick Coghlan wrote: > On 6 November 2017 at 02:02, Yury Selivanov wrote: > > On Fri, Nov 3, 2017 at 11:30 PM, Nick Coghlan wrote: > >> The current lack of DeprecationWarnings in 3.6 is a fairly