Philipp von Weitershausen wrote:
See below :). Of course, you don't have to deprecate zLOG instantly.
How else do you stop people still following the old patterns ;-)
I'm happy to sign up for this, but can't promise when it'll happen...
So let's schedule it for Zope 2.10 then :).
OK, I
Chris Withers wrote:
Philipp von Weitershausen wrote:
This would probably best be handled by one person, so if you are willing to
do all
the grepping and updating, making zLOG deprecated would just be a minor
operation :).
...but one i don't know how to perform. What code would I
Florent Guillaume wrote:
Just because you don't see the use in something doesn't mean it has to
go away.
There's nothing to stop you defining your own log levels with the python
logging module. I regularly (eg: MailingLogger) define a report level
that is 1 above INFO.
In my book BLATHER
Philipp von Weitershausen wrote:
This would probably best be handled by one person, so if you are willing to do
all the
grepping and updating, making zLOG deprecated would just be a minor operation
:).
...but one i don't know how to perform. What code would I insert and where?
I'm happy to
Tim Peters wrote:
[Dennis Allison]
We probably want an ALL level as well which would map to the NOTSET
of the Python logging code and log everything.
Why not call it NOTSET? Then you already have it ;-) Or forget it --
TRACE gets everything anyway.
Yeah, what he said ;-)
Also note that
[Tim Peters]
Also note that the code Florent pointed at is part of ZODB, not part
of Zope. Zope shouldn't use it directly. Growing its own copy would
be OK, or refactoring so that ZODB and Zope both get it from a shared
new mini-project.
[Chris Withers]
Sorry, which code are we talking
Chris Withers wrote:
Is zLOG deprecated?
If not, it should be...
+10
zLOG/__init__.py says:
Note:
This module exists only for backward compatibility. Any new code
for Zope 2.8 and newer should use the logging module from Python's
standard library directly. zLOG is only an
Philipp von Weitershausen wrote:
If not, it should be...
+10
Yeah, me too! Hence why I was asking ;-)
That means we could deprecate it even in Zope 2.9, using zLOG has
already been discouraged in Zope 2.8.
Cool, Andreas, can you make it start emitting deprecation warnings?
(if you do,
Chris Withers wrote:
# In the days of zLOG, there were 7 standard log levels, and
ZODB/ZEO used
# all of them. Here's how they map to the logging package's 5
standard
# levels:
#
#zLOG logging
#----
#
We probably want an ALL level as well which would map to the NOTSET
of the Python logging code and log everything.
Florent, I don't see a TRACE level in this list. Did you think one was
needed?
On Mon, 5 Dec 2005, Florent Guillaume wrote:
Chris Withers wrote:
# In the days of zLOG,
[Dennis Allison]
We probably want an ALL level as well which would map to the NOTSET
of the Python logging code and log everything.
Why not call it NOTSET? Then you already have it ;-) Or forget it --
TRACE gets everything anyway.
Florent, I don't see a TRACE level in this list. Did you
Chris Withers wrote:
Philipp von Weitershausen wrote:
If not, it should be...
+10
Yeah, me too! Hence why I was asking ;-)
That means we could deprecate it even in Zope 2.9, using zLOG has
already been discouraged in Zope 2.8.
Cool, Andreas, can you make it start emitting
12 matches
Mail list logo
