Serhiy Storchaka added the comment:
> However, this patch isn't right, since it will cause all source to be
> interpreted as UTF-8. This would be wrong when the sys.stdin.encoding is not
> UTF-8, and byte string objects are created in interactive mode.
Can you show how to reproduce the error that you're talking about? I have
found no issues running the bare Python and IDLE (with your patch, of course)
with files in different encodings under different locales.
Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list