[New-bugs-announce] [issue5556] interactive interpreter, source encoding
report at bugs.python.org
Tue Mar 24 20:32:02 CET 2009
New submission from Jean-Michel Fauth <wxjmfauth at gmail.com>:
A few hours ago I sent a comment to the issue #4626. I didn't notice the
issue was closed. So I repeat it here. I'm interested in comments
because I have the feeling it is still a pending annoying isssue.
I'm glad to have discovered this topic. I bumped into something similar
when I toyed with an interactive interpreter.
from code import InteractiveInterpreter
ii = InteractiveInterpreter()
source = ...
What should be the encoding and/or the type (str, bytes) of the "source"
string? Taking into account the encoding of the script which contains
this code, I have the feeling there is always something going wrong,
this can be a "non ascii" char in the source (encoded in utf-8!) or the
interactive interpreter does not accept very well a byte string
representing a utf-8 encoded string.
IDLE is not suffering from this. Its interactive interpreter is somehow
receiving "ucs-2 ready string" from tkinter.
I'm a little bit confused here (win2k, winXP sp2, Python 3.0.1).
components: Interpreter Core
title: interactive interpreter, source encoding
versions: Python 3.0
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce