[Web-SIG] Revising environ['wsgi.input'].readline in the WSGI specification
tseaver at palladion.com
Mon Nov 17 22:36:02 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
Manlio Perillo wrote:
> Phillip J. Eby ha scritto:
>> At 08:49 PM 11/17/2008 +0100, Manlio Perillo wrote:
>>> Ian Bicking ha scritto:
>>>> We need to propose a change to the WSGI specification. I propose, in
>>>> "Input and Error Streams"
>>>> (http://www.python.org/dev/peps/pep-0333/#input-and-error-streams) we
>>>> change it to have "readline(hint)" and expand Note 3 to include
>>>> readline as well as readlines, removing Note 2. Also I suppose some
>>>> sort of change note in the specification?
>>>> Does this sound like a sufficient change to the spec, and are there
>>>> any objections to the change?
>>> Fine for me, but of course we need to do this as:
>>> 1) Errata to WSGI 1.0
>>> 2) WSGI 1.1
>>> 3) WSGI 2.0
>>> You can't just modify the current WSGI 1.0 spec.
>>> I'm for 2), with the other clarifications about WSGI we have discussed
>>> in the past.
>> I'm more inclined towards #1.
> I'm not sure, since it is an API change; of course if there was an error
> in the API this should be an errata, but there is a rationale behind the
> current API.
> I'm fine, however, with an amendment.
Isn't the rationale completely defeated by the equivalent, relaxed form
for 'readlines' (note #3). That was why I voted +1: I couldn't see
that relaxing 'readline' to match 'readlines' would make life any harder
on server implementers.
Tres Seaver +1 540-429-0999 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Web-SIG