Re: [ZODB-Dev] Re: [Zope-dev] Re: zLOG module deprecated
On 1/9/06, Andreas Jung <lists@andreas-jung.com> wrote:
I've never had the need to use them.
No, but other people do.
That's different from not wanting to use them. The more choice you have, the more trouble you have. I agree that a TRACE level might be of interest. But BLATHER and PROBLEM is competely overhead from my point of view - in fact I can't explain when to use BLATHER or TRACE compared to DEBUG.
But I can, and so can Florent. "PROBLEM" I agree about. I have never heard that one before, and I don't see why you can't use ERROR or WARNING. ERROR: Something didn't work. WARNING: There is something fishy here, I'm guessing how it should be handled. INFO: Nothing is wrong, but this is important. (For example Zope server ready to handle requests). VERBOSE: Nothing is wrong and this may be important. (For example the info saying what IP-adress and port the zope server is started on.) DEBUG: For debug information. TRACE: I need to have a lot of information now! I find all this fairly self-evident and highly useful, and se absolutely zero reason for removing them, when they are so useful. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/
--On 10. Januar 2006 10:51:04 +0100 Lennart Regebro <regebro@gmail.com> wrote:
I find all this fairly self-evident and highly useful, and se absolutely zero reason for removing them, when they are so useful.
This decision was made for Zope 2.8 (according to zLOG/__init__.py). We're now working on Zope 2.10. What is the problem adding these levels in your application if needed? Also Zope 3 is not using a dedicated z3LOG module or whatever. I still don't see the need for one. If there is need for one then this should be solved as common solution for Zope 3 and Zope 2. -aj
Lennart Regebro wrote:
I've never had the need to use them.
No, but other people do.
That's different from not wanting to use them. The more choice you have, the more trouble you have. I agree that a TRACE level might be of interest. But BLATHER and PROBLEM is competely overhead from my point of view - in fact I can't explain when to use BLATHER or TRACE compared to DEBUG.
But I can, and so can Florent.
"PROBLEM" I agree about. I have never heard that one before, and I don't see why you can't use ERROR or WARNING.
Stop focusing on 'PROBLEM', it's just an alias for 'WARNING'. Florent
ERROR: Something didn't work. WARNING: There is something fishy here, I'm guessing how it should be handled. INFO: Nothing is wrong, but this is important. (For example Zope server ready to handle requests). VERBOSE: Nothing is wrong and this may be important. (For example the info saying what IP-adress and port the zope server is started on.) DEBUG: For debug information. TRACE: I need to have a lot of information now!
I find all this fairly self-evident and highly useful, and se absolutely zero reason for removing them, when they are so useful.
-- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg@nuxeo.com
participants (3)
-
Andreas Jung -
Florent Guillaume -
Lennart Regebro