Comment 1 for bug 1089827

Michael Nelson (michael.nelson) wrote :

AFAICT, the cause is a change between twisted releases 11.0.0 and 11.1.0.

Our staging server (waxapple) had 11.1.0 installed yesterday [1], although I can't be certain from which version it was upgraded from the info that I have.

The line causing the IOError is accessing stdout in the 11.1.0 twisted release [2], which is not accessed at all in the twisted 11.0.0 release [3].

Our production service is still running with python-twisted-core 10.0.0 [4].

As this will effect any wsgi service using txstatsd, I'll mark it as affected also, although we can probably just use the WSGIRestrictStdout directive to avoid the exception.