Tres Seaver wrote:
I've noticed a couple of problems with recent deprecation decisions (for
OFS.content_types and zLOG). The major one is that the deprecation
warning waw added without removing the code in the core which depends on
the deprecated feature. The most obvious sign of this is that the tests
no longer "run clean", but are cluttered up with warning output.
Yes this is a major pain. Such that in my sandboxes the first thing I do is
comment out the warning in zLOG.
Florent
Another issue is that at least one of those choices (the zLOG one)
seemed to land without accounting for the legitimate use cases which the
new "blessed" method doesn't address (e.g, logging levels not offered by
the standard 'logging' module).
I'm about to check in changes which clean out the use of
OFS.content_types, but am less willing to clean up the zLOG uses until
the other use cases are addressed.
--
Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
