[Python-Dev] Pronouncement needed in issue9675 (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Tue Sep 28 23:59:55 CEST 2010

On Tue, Sep 28, 2010 at 11:49 PM, Guido van Rossum <guido at python.org> wrote:

It strikes me that in general deprecation warnings in 2.7 don't do anybody any good unless they're Py3k warnings. It sounds to me that there is no shame in removing the warning in Python 2.7 (or turning it into a Py3k warning -- nobody should expect their code to behave well when Py3k warnings are turned into errors). My guess is that the warning was added to 2.7 before it was clear that there would never be a 2.8.

At the same time I don't want to go so far as to remove all remaining deprecation warnings from 2.7.1 (too  much churn) -- but for this specific one it sounds like a reasonable compromise.

Converting to a Py3k warning sounds like the best option.

Cheers, Nick.

-- Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list