[stdlib-sig] standardizing the deprecation policy (and how noisy they are)
g.brandl at gmx.net
Mon Nov 9 20:40:48 CET 2009
Brett Cannon schrieb:
> On Sun, Nov 8, 2009 at 16:53, Georg Brandl <g.brandl at gmx.net> wrote:
>> Brett Cannon schrieb:
>>> During the moratorium PEP discussions Guido said he wanted to quiet
>>> down deprecation warnings. I see there being two options on this.
>>> One is to keep things as is, but to require two releases with
>>> PendingDeprecationWarning so there are three years of
>>> silent-by-default warnings to update your code. But that last release
>>> before removal came would still be noisy.
>>> The other option is to simply have all warnings filtered out by
>>> default. We could alter -W so that when it is used w/o an argument it
>>> turns to what is currently the default behaviour (or even turn all
>>> warnings which is more than what happens now).
>> As a technical note, optional option arguments are a bad idea.
>> python -W ignore
>> Am I calling the file "ignore" with all warnings enabled or running the
>> interactive interpreter ignoring all warnings?
> You are calling the file called "ignore"; the argument to -W must
> contain colons to be valid.
It doesn't need to now; and IMO that is quite helpful, since it allows e.g. a
very short -Wi argument without me having to remember just how many colons
I have to put there.
And even if that change is deemed to be fine, why shouldn't I have colons in
my filename? Special cases are not special enough... ;)
More information about the stdlib-sig