➜

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 THRlWiTi
Recipients Geraldo.Xexeo, THRlWiTi, Tomoki.Imai, alex.hartwig, asvetlov, ezio.melotti, kbk, loewis, ned.deily, pradyunsg, r.david.murray, roger.serwy, serhiy.storchaka, terry.reedy
Date 2013-11-17.15:37:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384702639.35.0.637795726869.issue15809@psf.upfronthosting.co.za>
In-reply-to
Content 
Well, if there is no other way around this, I think it's better to apply Martin's patch. At least then we will be able to enter any valid utf-8 character in IDLE (although print statement won't print correctly unless the string is decoded first).

(As a Windows user, currently I can't print u'йцук' in interactive mode and get an "Unsupported characters in input" error because my default system encoding (cp1256) can't encode Russian.)

Also it will be more Unicode friendly which is not a bad thing.
History
Date User Action Args
2013-11-17 15:37:19THRlWiTisetrecipients: + THRlWiTi, loewis, terry.reedy, kbk, ned.deily, ezio.melotti, roger.serwy, r.david.murray, asvetlov, Geraldo.Xexeo, serhiy.storchaka, alex.hartwig, pradyunsg, Tomoki.Imai
2013-11-17 15:37:19THRlWiTisetmessageid: <1384702639.35.0.637795726869.issue15809@psf.upfronthosting.co.za>
2013-11-17 15:37:19THRlWiTilinkissue15809 messages
2013-11-17 15:37:18THRlWiTicreate