Re: WSGIRequest._stream.read() blocking

> Isn't this the same bug as and ? Yes. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.go

Re: WSGIRequest._stream.read() blocking

Thanks Roberto, We had UWSGI 0.9.6.8 installed first. Now I did an upgrade to 0.9.8 and now everything works perfect. Thanks a lot for the quick response. On 14 juin, 15:00, Roberto De Ioris wrote: > Il giorno 14/giu/2011, alle ore 14.54, Jonathan Slenders ha scritto: > > > > > > > > > > > Hi

Re: WSGIRequest._stream.read() blocking

Hi Jonathan, Isn't this the same bug as and ? Best regards, -- Aymeric Augustin. 2011/6/14 Jonathan Slenders > if I replace: > > > if type(socket._fileobject) is type and > isinstance(self.environ['wsg

Re: WSGIRequest._stream.read() blocking

Il giorno 14/giu/2011, alle ore 14.54, Jonathan Slenders ha scritto: > Hi all, > > > Using WSGI on production environment: > > In django.core.handlers.wsgi.py is a clear notice that wsgi.input, > which can be an instance of socket._fileobject will hang when reading > past the available count.

Re: WSGIRequest._stream.read() blocking

if I replace: > if type(socket._fileobject) is type and > isinstance(self.environ['wsgi.input'], socket._fileobject): by: > if True in django.core.handlers.wsgi.py Then, everything works perfect, so it has to be in this check. -- You received this message because you are subscribed to the Go

WSGIRequest._stream.read() blocking

Hi all, Using WSGI on production environment: In django.core.handlers.wsgi.py is a clear notice that wsgi.input, which can be an instance of socket._fileobject will hang when reading past the available count. In my case, wsgi.input appears to be of the type 'file', so the following test fails,