Serhiy Storchaka added the comment: When someone reads file in locale encoding (either as str or unicode in 2.7), he gets printable result. When someone lists directory, he gets printable result (str or unicode). When someone enter string literal (either str or unicode) in interactive mode, he gets printable result. This is expected behavior. And this means that default encoding for text files, filesystem encoding and encoding used in interactive Python (or IDLE console) should be the same, locale encoding.
> Irdb said "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.)" This is different issue. It would be better if IDLE will filter pasted text and replace unencodable characters or underscore them with wavy red line. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15809> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
