Want to co-design and implement a logging module?
I'd like to see a logging module in the standard Python library. Is anybody interested in helping spec out requirements and work on an implementation? Some ideas from Zope's zLOG module should probably go into it (it should eventually be a replacement for that), and some from log4j (http://jakarta.apache.org/log4j/docs/). Any takers? --Guido van Rossum (home page: http://www.python.org/~guido/)
Guido van Rossum wrote:
I'd like to see a logging module in the standard Python library. Is anybody interested in helping spec out requirements and work on an implementation? Some ideas from Zope's zLOG module should probably go into it (it should eventually be a replacement for that), and some from log4j (http://jakarta.apache.org/log4j/docs/).
Any takers?
I'm not sure I'm a "taker", but I did a bit of research and found log4p, http://log4p.sourceforge.net/ Have you looked at it, and if yes, what's a short reason why it wouldn't be suitable? (One of the things I disliked about Zlogger (I believe that's the correct name) is that it seems to require an error tuple, based on what I'm reading in http://www.zope.org/Documentation/Misc/LOGGING.txt I believe that loggers should be more generic.) -- --- Aahz (@pobox.com) Hugs and backrubs -- I break Rule 6 <*> http://www.rahul.net/aahz/ Androgynous poly kinky vanilla queer het Pythonista We must not let the evil of a few trample the freedoms of the many.
aahz@rahul.net (Aahz Maruch) writes:
I'm not sure I'm a "taker", but I did a bit of research and found log4p, http://log4p.sourceforge.net/
Have you looked at it, and if yes, what's a short reason why it wouldn't be suitable?
The thing I dislike about log4p is that it looks much to java-ish. import java.util.DateFormat; is not something I would like to do when using the standard Python library. Regards, Martin
Guido van Rossum wrote:
I'd like to see a logging module in the standard Python library. Is anybody interested in helping spec out requirements and work on an implementation? Some ideas from Zope's zLOG module should probably go into it (it should eventually be a replacement for that), and some from log4j (http://jakarta.apache.org/log4j/docs/).
Any takers?
You might want to have a look at mx.Log which is part of the egenix-mx-base distribution. It is undocumented, but reading the source should give some insights. The basic idea is that you have logging objects which are usually created as singletons; these can then log various information depending on a fine grained verbosity level to a log file, stdout or stderr. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
On Sun, Feb 03, 2002 at 09:35:25PM -0500, Guido van Rossum wrote:
I'd like to see a logging module in the standard Python library. Is anybody interested in helping spec out requirements and work on an implementation? Some ideas from Zope's zLOG module should probably go into it (it should eventually be a replacement for that), and some from log4j (http://jakarta.apache.org/log4j/docs/).
Any takers?
I'll take it. I have been (slowly) working on a log4j translation, trying to stay as close to log4j's API as possible. I'll take a look at zLOG. [Aahz said]
I'm not sure I'm a "taker", but I did a bit of research and found log4p, http://log4p.sourceforge.net/
That one has not seen any development for ages and I don't believe it is even functional. There *is* a log4py out there. http://www.its4you.at/log4py.php http://sourceforge.net/project/showfiles.php?group_id=36216 I took a quick look at it a while ago and thought it was pretty limited. Perhaps not though -- I may have been sufferring from a bout of "Not invented here." [MAL said:]
You might want to have a look at mx.Log which is part of the egenix-mx-base distribution. It is undocumented, but reading the source should give some insights.
The basic idea is that you have logging objects which are usually created as singletons; these can then log various information depending on a fine grained verbosity level to a log file, stdout or stderr.
Sounds very similar to log4j. I'll take a look at that too. Note that the log4j manual that is currently up (http://jakarta.apache.org/log4j/docs/manual.html) is for the current release version. They have an alpha version that cleans up the naming a little bit mainly, I think, to try to make log4j look a little bit more like the java.util.logging API. Actually, log4j's site *used* to have a bunch of other pages up their that included links to contributed packages and ports of log4k to other languages (C, C++, Perl, Python, etc). How about I try to have a PEP together within a week or two, and perhaps a working base implementation? Trent -- Trent Mick TrentM@ActiveState.com
On 04 February 2002, Trent Mick volunteered to "do something" about a standard logging module for Python:
How about I try to have a PEP together within a week or two, and perhaps a working base implementation?
Well, it's been exactly 7 days. Trent, are you halfway done yet? ;-) (Yes, I've been thinking that the solution to the Distutils' verbosity problem lies somewhere down this road.) Greg -- Greg Ward - Unix geek gward@python.net http://starship.python.net/~gward/ Laziness, Impatience, Hubris.
On Mon, Feb 11, 2002 at 10:03:38AM -0500, Greg Ward wrote:
On 04 February 2002, Trent Mick volunteered to "do something" about a standard logging module for Python:
How about I try to have a PEP together within a week or two, and perhaps a working base implementation?
Well, it's been exactly 7 days. Trent, are you halfway done yet? ;-)
I have my thoughts together. I'll write up and post tonight. Meanwhile I have to get some work done for my employer. :) Regarding Distutils for Python 1.5.2 usage: the potential logging support *could* be back ported and included in the distutils package that gets put together for Python 1.5.2. Trent -- Trent Mick TrentM@ActiveState.com
participants (8)
-
aahz＠rahul.net -
barry＠zope.com -
Greg Ward -
Guido van Rossum -
M.-A. Lemburg -
martin＠v.loewis.de -
Tim Peters -
Trent Mick