Graham Dumpleton ha scritto:
[...]
Here is the culprit:
http://lists.alioth.debian.org/pipermail/python-modules-team/2009-January/003514.html
http://code.google.com/p/modwsgi/issues/detail?id=82
So it seems safe, when the Log object used in wsgi.errors is also used
to replace sys.stderr,
On Tue, Mar 30, 2010 at 11:28, Manlio Perillo manlio_peri...@libero.it wrote:
Note however, that Mercurial has fixed the problem:
So, as the guy who inherited Mercurial's hgweb WSGI application (or
rather, made it much more WSGI-compliant), I should say that, yes, I
tried pretty hard to get all
On Tue, Mar 30, 2010 at 11:44, Manlio Perillo manlio_peri...@libero.it wrote:
Did you managed to remove usage of the write callable?
Yes, I think we haven't been using that for a few versions now.
Cheers,
Dirkjan
___
Web-SIG mailing list
...
It is all very silly. Technically a file like object is not
required
to have a 'closed' attribute, so that code expecting it was
wrong in
the first place.
All you can really do is supply as many of the methods,
attributes as
possible, all required and as many as optional as makes
