[stdlib-sig] standardizing the deprecation policy (and hownoisy they are)
debatem1 at gmail.com
Wed Nov 11 00:40:36 CET 2009
On Tue, Nov 10, 2009 at 6:00 PM, Ben Finney <ben+python at benfinney.id.au> wrote:
> geremy condra <debatem1 at gmail.com> writes:
>> On Tue, Nov 10, 2009 at 1:19 PM, Guido van Rossum <guido at python.org> wrote:
>> > On Tue, Nov 10, 2009 at 8:50 AM, geremy condra <debatem1 at gmail.com> wrote:
>> >> If you're so worried about the warnings, suppress them. You control
>> >> the code.
>> > No. The nuisance of warnings is that they are presented to the
>> > *user*, not the developer, and the user (in many cases) doesn't
>> > control the code.
>> > --
>> > --Guido van Rossum (python.org/~guido)
>> In this case, however, he does, as per his comment:
> Antoine (“he”, in your sentence) does. *The user does not*, and it is
> the user who is seeing the warnings:
...and so he (Antoine) should suppress the warnings if he is
worried about the user seeing them. Unless he's operating
on an incredibly slow release schedule his users will see his
patch a *long* time before they'll see any change in their
default version of python's behavior.
More information about the stdlib-sig