[issue2384] [Py3k] line number is wrong after encoding declaration

Amaury Forgeot d'Arc report at bugs.python.org
Fri Oct 10 01:45:28 CEST 2008


Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

Committed r66867. 

I had to considerably change the unit tests, because the subprocess 
output is not utf-8 encoded; it's not even the same as sys.stdout, 
because the spawned process uses a PIPE, not a terminal: on my winXP, 
the main interpreter uses cp437, but the subprocess says cp1252. So I 
first run a 'python -c "print(sys.stdout.encoding)"' in the same 
conditions just to retrieve the encoding. fun fun.
I hope this still works on Unixes, will watch the buildbots.

----------
resolution:  -> fixed
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue2384>
_______________________________________


More information about the Python-bugs-list mailing list