On 21/12/2007, Brian Smith <[EMAIL PROTECTED]> wrote:
> The
> specification should then also explicitly say that WSGI applications
> should not redirect logging output to wsgi.errors or anywhere else. In
> fact, if that was done, there would be no reason to have wsgi.errors in
> the first place.
A
At 07:44 AM 12/21/2007 +0700, Brian Smith wrote:
>In
>fact, if that was done, there would be no reason to have wsgi.errors in
>the first place.
There are other logging systems out there besides the Python logging
module -- and some of them are better for their specific
purposes. And the Python
Graham Dumpleton wrote:
> > > However there are some problems.
> > > The log object has a fixed error level (NGX_LOG_ERR);
> > > this means that every message logged using this object
> > > will have this error level, even if I do, as example:
> > > log.info('just an info message')
> >
> > I'm miss
On 21/12/2007, Chris Withers <[EMAIL PROTECTED]> wrote:
> Manlio Perillo wrote:
> >> For me, it does feel like the responsibility of the server to
> >> configure logging, and I think this is something that should be
> >> documented somewhere. Afterall, as you guys have been discussing, it's
> >> th
Manlio Perillo wrote:
>> For me, it does feel like the responsibility of the server to
>> configure logging, and I think this is something that should be
>> documented somewhere. Afterall, as you guys have been discussing, it's
>> the server that holds configuration for things like listening soc
At 01:27 PM 12/20/2007 +0100, Manlio Perillo wrote:
>Hi.
>
>It seems that there is a little error in the WSGI spec.
>
>In the "Specification Details" chapter there is this note:
>
>"""(Note: the application must invoke the start_response() callable
>before the iterable yields its first body string,
On 20 Dec 2007, at 07:27, Manlio Perillo wrote:
> What's wrong is that the invocation of start_response may be performed
> at any iteration of the iterable, as long as the application yields
> empty strings.
In what context? I suspect that's an error in a particular
implementation, not in the s
Hi.
It seems that there is a little error in the WSGI spec.
In the "Specification Details" chapter there is this note:
"""(Note: the application must invoke the start_response() callable
before the iterable yields its first body string, so that the server can
send the headers before any body c
