Robin Schoonover added the comment:
I'm not sure I follow, as it has little to say on whether the application's
expected behavior here, and only a recommendation that the server allow it.
But, it also defers to the "Python Standard Library", which does have an
opini
Changes by Robin Schoonover :
Added file: http://bugs.python.org/file35836/wsgiref-empty-byte-3.patch
___
Python tracker
<http://bugs.python.org/issue21890>
___
___
Pytho
Robin Schoonover added the comment:
I agree, the current patch is too permissive.
Both a server I wrote a while ago, and most other "complaint" servers deal with
the problem the exact same way as that patch, and that extra permissiveness led
to my misinterpretation when analyzing
Robin Schoonover added the comment:
Fair enough, I misled myself.
However, and I feel like I'm getting really picky here, but it still doesn't
fulfill the paragraph I quoted:
def application(environ, start_response):
start_response('200 OK',
Changes by Robin Schoonover :
--
nosy: +pje
___
Python tracker
<http://bugs.python.org/issue18610>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Robin Schoonover:
Consider this paragraph of PEP, referring to headers obtained
via start_response, emphasis mine:
Instead, it must store them for the server or gateway to
transmit only after the first iteration of the application
return value that yields a
Changes by Robin Schoonover :
--
keywords: +patch
Added file: http://bugs.python.org/file35810/wsgiref-empty-byte.patch
___
Python tracker
<http://bugs.python.org/issue21
Robin Schoonover added the comment:
Issue also occurs if .read() is used with no size.
--
title: wsgi.simple_server's wsgi.input readline waits forever for
non-multipart/form-data -> wsgi.simple_server's wsgi.input read/readline waits
forever in certain
New submission from Robin Schoonover:
In the reference WSGI server in wsgiref.simple_server, wsgi.input's readline()
hangs if the request body does not actually contain any
newlines.
Consider the following (slightly silly) example:
from wsgiref.simple_server import make_server
Changes by Robin Schoonover :
--
title: wsgiref.validator expects wsgi.input read to give exactly one arg ->
wsgiref.validate expects wsgi.input read to give exactly one arg
___
Python tracker
<http://bugs.python.org/issu
New submission from Robin Schoonover:
wsgiref.validator requires wsgi.input's read to always give EXACTLY one
argument. This is incorrect.
It's own documentation says:
* That wsgi.input is used properly:
- .read() is called with zero or one argument
PEP says:
A server should
Robin Schoonover added the comment:
Since these sort of buffer objects don't exist in 3.x (so far as I know), I
came up with a different way to test in 3.x (basically, trying to pickle bound
or unbound methods).
It turns out that using this method to test it in 2.6 seems to fail whe
New submission from Robin Schoonover :
The multiprocessing module's version of the Queue class, which causes objects
to be pickled for process to process transfer, ignores pickle restrictions when
objects are added to the queue. Example code (buffer isn't pickleable):
Changes by Robin Schoonover :
--
nosy: +rschoon
___
Python tracker
<http://bugs.python.org/issue3871>
___
___
Python-bugs-list mailing list
Unsubscribe:
14 matches
Mail list logo
