This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients alex.hartwig, asvetlov, ezio.melotti, loewis, serhiy.storchaka, terry.reedy
Date 2012-11-12.12:19:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1352722788.45.0.773310842292.issue15809@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2012-11-12 12:19:48serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, terry.reedy, ezio.melotti, asvetlov, alex.hartwig
2012-11-12 12:19:48serhiy.storchakasetmessageid: <1352722788.45.0.773310842292.issue15809@psf.upfronthosting.co.za>
2012-11-12 12:19:48serhiy.storchakalinkissue15809 messages
2012-11-12 12:19:48serhiy.storchakacreate