I am testing if there are some global WSGI issues running the build in
wsgi 3.1 server
def application(environ, response):
range=environ.get('HTTP_RANGE','bytes=0-').replace
('bytes=','').split(',')
offset=[]
for r in range: offset.append(r.split('-'))
out='0123456789'
On 06-08-2009, Damjan wrote:
Not very well.
We are having another argument about WSGI specification and Python 3.0
at the moment on Python WEB-SIG list. The discussion seems to have
exploded over night and have about 30 messages to read about it yet.
If some sort of resolution isn't
On Aug 6, 8:44 pm, Damjan gdam...@gmail.com wrote:
Not very well.
We are having another argument about WSGI specification and Python 3.0
at the moment on Python WEB-SIG list. The discussion seems to have
exploded over night and have about 30 messages to read about it yet.
If some
This is not the list for WSGIServer so perhaps go ask the authors instead.
Am not surprised they wouldn't be supporting HTTP/1.1 in response as
implementing keep alive and chunked content is a pain.
Graham
2009/8/7 gert gert.cuyk...@gmail.com:
I am testing if there are some global WSGI
