RetroSearch Browse

Thu Feb 16 04:40:12 CET 2012 · https://mail.python.org/pipermail/python-dev/2012-February/116541.html

On Feb 13, 2012, at 8:44 PM, Nick Coghlan wrote:

> On Tue, Feb 14, 2012 at 2:25 PM, Eli Bendersky <eliben at gmail.com> wrote:
>> With the deprecation warning being silent, is there much to lose, though?
> 
> Yes, it creates problems for anyone that deliberately converts all
> warnings to errors when running their test suites. This forces them to
> spend time switching over to a Python version dependent import of
> either cElementTree or ElementTree that could have been spent doing
> something actually productive instead of mere busywork.
> 
> And, of course, even people that *don't* convert warnings to errors
> when running tests will have to make the same switch when the module
> is eventually removed.

What about a PendingDeprecationWarning? I think you're usually only going to convert DeprecationWarnings to errors (with python -W error::DeprecationWarning or warnings.simplefilter('error', DeprecationWarning))

--
Philip Jenvey

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-February/116541.html below:

[Python-Dev] folding cElementTree behind ElementTree in 3.3