The tokenizer gets b"u'\xce\xb1'" by calling PyOS_Readline and it knows it's utf-8 encoded. But the result of evaluation is u'\xce\xb1'. Because of how eval works, I believe that it would work correctly if the PyCF_SOURCE_IS_UTF8 was set, but it is not. That is why I'm asking if there is a way to set it. Also, my naive thought is that it should be always set in the case of interactive session.u'\xce\xb1'Yes, that works for eval. But I want it for code entered during an interactive session.>>> u'α'On Wed, Apr 29, 2015 at 4:59 PM, Victor Stinner <firstname.lastname@example.org> wrote:
Le 29 avr. 2015 10:36, "Adam Bartoš" <email@example.com> a écrit :
> Why I'm talking about PyCF_SOURCE_IS_UTF8? eval(u"u'\u03b1'") -> u'\u03b1' but eval(u"u'\u03b1'".encode('utf-8')) -> u'\xce\xb1'.
There is a simple option to get this flag: call eval() with unicode, not with encoded bytes.
Python-Dev mailing list