[EMAIL PROTECTED] wrote: > Python's InteractiveInterpreter uses the built-in compile function. > > According to the ref. manual, it doesn't seem to concern about the > encoding of the source string. > > When I hand in an unicode object, it is encoded in utf-8 automatically. > It can be a problem when I'm building an interactive environment using > "compile", with a different encoding from utf-8. IDLE itself has the > same problem. ( '<a string with non-ascii-encoding>' is treated okay > but u'<a string with non-ascii-encoding>' is treated wrong.) > > Any suggestions or any plans in future python versions?
I've read a posting from Martin Von Loewis mentioning trying to build in that feature(optionally marking encoding when calling "compile"). Anyone knows how it is going on? -- http://mail.python.org/mailman/listinfo/python-list
