On Fri, Sep 10, 2010 at 14:55, Daniel Stutzbach
wrote:
> On Fri, Sep 10, 2010 at 3:32 PM, Georg Brandl wrote:
>>
>> IMO this runs contrary to the decision we made when DeprecationWarnings
>> were
>> made silent by default: it spews messages not only at developers, but also
>> at
>> users, who don
On Sat, Sep 11, 2010 at 9:42 AM, Glyph Lefkowitz
wrote:
>
> On Sep 10, 2010, at 5:10 PM, Amaury Forgeot d'Arc wrote:
>
>> 2010/9/10 Fred Drake :
>>> On Fri, Sep 10, 2010 at 4:32 PM, Georg Brandl wrote:
IMO this runs contrary to the decision we made when DeprecationWarnings
were
ma
On Sep 10, 2010, at 5:10 PM, Amaury Forgeot d'Arc wrote:
> 2010/9/10 Fred Drake :
>> On Fri, Sep 10, 2010 at 4:32 PM, Georg Brandl wrote:
>>> IMO this runs contrary to the decision we made when DeprecationWarnings were
>>> made silent by default: it spews messages not only at developers, but als
On Fri, Sep 10, 2010 at 3:32 PM, Georg Brandl wrote:
> IMO this runs contrary to the decision we made when DeprecationWarnings
> were
> made silent by default: it spews messages not only at developers, but also
> at
> users, who don't need it and probably are going to be quite confused by it,
> a
Georg Brandl writes:
> it prints a warning (...) at interpreter shutdown if gc.garbage is nonempty.
>
> IMO this runs contrary to the decision we made when DeprecationWarnings were
> made silent by default
>
> Opinions?
Agreed, this should be reverted for the reasons you give but DO LEAVE THIS
2010/9/10 Fred Drake :
> On Fri, Sep 10, 2010 at 4:32 PM, Georg Brandl wrote:
>> IMO this runs contrary to the decision we made when DeprecationWarnings were
>> made silent by default: it spews messages not only at developers, but also at
>> users, who don't need it and probably are going to be qu
On Fri, Sep 10, 2010 at 4:32 PM, Georg Brandl wrote:
> IMO this runs contrary to the decision we made when DeprecationWarnings were
> made silent by default: it spews messages not only at developers, but also at
> users, who don't need it and probably are going to be quite confused by it,
Agreed;
Hey #python-dev,
I'd like to ask your opinion on this change; I think it should be reverted
or at least made silent by default. Basically, it prints a warning like
gc: 2 uncollectable objects at shutdown:
Use gc.set_debug(gc.DEBUG_UNCOLLECTABLE) to list them.
at interpreter shut
