RetroSearch Browse

Sun Feb 21 21:00:00 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-February/097846.html

On Sun, Feb 21, 2010 at 14:46, Eric Smith <eric at trueblade.com> wrote:

> Brett Cannon wrote:
>
>> Yes, DeprecationWarning is now silent under Python 2.7 and 3.1 so a
>> DeprecationWarning would only pop up if developers exposed
>> DeprecationWarning. But if the module is not about to be removed in 3.x then
>> I think regardless of the silence of both warnings it should stay
>> PendingDeprecationWarning.
>>
>
> But if we're never going to change it to a DeprecationWarning, it's not
> pending.

Well, it's pending until Py4K, so it's accurate, we just don't know yet when
it will change to an actual deprecation. =)

> So why not just change the docs and not add any warnings to the code?

Could, but the code will go away some day and not everyone will read the
docs to realize that they might want to upgrade their code if they care to
use the shiniest thing in the standard library.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100221/a472bdd3/attachment-0001.html>

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

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

[Python-Dev] some notes from the first part of the lang summit