On Sep 10, 2010, at 5:10 PM, Amaury Forgeot d'Arc wrote: > 2010/9/10 Fred Drake <[email protected]>: >> On Fri, Sep 10, 2010 at 4:32 PM, Georg Brandl <[email protected]> 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; this should be silent by default. > > +1. I suggest to enable it only when Py_DEBUG (or Py_TRACE_REFS or > Py_REF_DEBUG?) is defined.
Would it be possible to treat it the same way as a deprecation warning, and show it under the same conditions? It would be nice to know if my Python program is leaking uncollectable objects without rebuilding the interpreter. _______________________________________________ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
