Phillip J. Eby ha scritto:
> At 08:34 PM 1/17/2008 +0100, Manlio Perillo wrote:
>> Hi.
>>
>> What is the rationale for Headers._headers being private?
>
> The code was mostly a copy-and-paste job from email.Message, which did
> the same. At one point, it might actually have been a subclass of
>
At 08:34 PM 1/17/2008 +0100, Manlio Perillo wrote:
>Hi.
>
>What is the rationale for Headers._headers being private?
The code was mostly a copy-and-paste job from email.Message, which
did the same. At one point, it might actually have been a subclass
of email.Message, and so it was required.
_
Hi.
What is the rationale for Headers._headers being private?
Thanks Manlio Perillo
___
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/options/web-sig/archive%40mail-arc
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
