Login | Register
My pages Projects Community openCollabNet
Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Reply to message

* = Required fields
* Subject
* Body
Attachments
Send reply to
Topic
Author (directly in email)
Please type the letters in the image above.

Original message

Author Jared Greenwald <greenwaldjared@gmail.com>
Full name Jared Greenwald <greenwaldjared@gmail.com>
Date 2006-08-30 19:56:46 PDT
Message Why is there even a need for logger.py anyway? Why not just
initialize the logging module in the global current/__init__.py? Then
there's no wrapper logger.log anymore, just call directly into
logging.log - that would make things a whole lot simpler.

(Again, I'm a bit of a python n00b, so I might be totally wrong.)

-Jared

On 8/30/06, Jack Neely <jjneely at gmail dot com> wrote:
> > Oh, one remark about the log code in user.py, either I'm getting
> > dumb, or you have placed the level in the wrong position.
> > (short pauze) no, i'm right. grep agrees with me.
> >
>
> But they both work ;-)
>
> You know I find it next to impossible to make things consistant.
> Hunter's logger.py code had stuff so you did log("message", level)
> while every other logging code on the face of the planet it seems does
> log(level, "message"). Which caused me no end of confusion while
> trying to remember how to log something.
>
> I'd like to make everything log(level, message). I *should* just say
> screw it and make everything log(message, level).
>
> > Another, slightly feature request: it might be handy to invalidate
>
> Indeed.
>
> Jack
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@curr​ent.tigris.org
> For additional commands, e-mail: dev-help at current dot tigris dot org
>
>