[issue10479] cgitb.py should assume a binary stream for output

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python

[issue10479] cgitb.py should assume a binary stream for output

Glenn Linderman added the comment: So since cgi.py was fixed to use the .buffer attribute of sys.stdout, that leaves sys.stdout itself as a character stream, and cgitb.py can successfully write to that. If cgitb.py never writes anything but ASCII, then maybe that should be documented, and th

[issue10479] cgitb.py should assume a binary stream for output

Changes by Antoine Pitrou : -- nosy: +facundobatista, fdrake, orsenthil versions: +Python 3.1 ___ Python tracker ___ ___ Python-bugs-l

[issue10479] cgitb.py should assume a binary stream for output

Changes by Glenn Linderman : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue10479] cgitb.py should assume a binary stream for output

New submission from Glenn Linderman : The CGI interface is a binary stream, because it is pumped directly to/from the HTTP protocol, which is a binary stream. Hence, cgitb.py should produce binary output. Presently, it produces text output. When one sets stdout to a binary stream, and then c