Manlio Perillo wrote:
> The interface of the python logging is:
>log(level, msg[, *args[, **kwargs]])
> right?
>
>
> The problem with this is that, as an example, Twisted logging system
> does not knows about log levels.
>
> Moreover, the message formatting is not done by the logging system
Manlio Perillo wrote:
>> I don't really see how this helps. If it's optional, then ever wsgi
>> app will need a bunch of if/then/else to decide if this method can be
>> called and what to do instead.
>>
> This is not a problem. The job can be done by a middleware.
...which everyone will then hav
Chris Withers ha scritto:
> Manlio Perillo wrote:
>>
>> wsgi.errors maybe should have an optional method:
>> .msg(level, *args)
>>
>> where args is a list of strings
>>
>> or
>> .msg(*args, **kwargs)
>>
>> where the keys in kwargs are implementation defined.
>
> I don't really see how this helps.
Manlio Perillo wrote:
>
> wsgi.errors maybe should have an optional method:
> .msg(level, *args)
>
> where args is a list of strings
>
> or
> .msg(*args, **kwargs)
>
> where the keys in kwargs are implementation defined.
I don't really see how this helps. If it's optional, then ever wsgi app
Chris Withers ha scritto:
> Phillip J. Eby wrote:
>> And how is, say, an SQL connection object supposed to know what the
>> "page path" is? That was the whole point of this thread: that without
>> passing logger objects around, or having some other dynamic context,
>> there's no way for librari
Phillip J. Eby wrote:
> And how is, say, an SQL connection object supposed to know what the
> "page path" is? That was the whole point of this thread: that without
> passing logger objects around, or having some other dynamic context,
> there's no way for libraries to direct their log informati
