[issue5556] interactive interpreter, source encoding

2010-08-27 Thread Terry J. Reedy
Terry J. Reedy tjre...@udel.edu added the comment: Additional note: RefMan 2. Lexical analysis: Python reads program text as Unicode code points; Doc for runsource says Compile and run some source in the interpreter. Arguments are the same as for compile_command(). Latter says sourse is the

[issue5556] interactive interpreter, source encoding

2010-08-26 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: Agreed. Although the docs do not explicitly say you cannot use bytes as source, this is clearly implicit in the Python3 bytes/string separation. The docs talk only about string inputs. -- nosy: +r.david.murray resolution: -

[issue5556] interactive interpreter, source encoding

2010-07-09 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +amaury.forgeotdarc stage: - unit test needed versions: +Python 2.7, Python 3.1, Python 3.2 -Python 3.0 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5556

[issue5556] interactive interpreter, source encoding

2010-07-09 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: I fail to see the issue. runsource() takes a (unicode) string because a Python script is a text; you cannot pass a bytes object, it must be decoded before. -- ___ Python tracker

[issue5556] interactive interpreter, source encoding

2010-07-09 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5556 ___ ___ Python-bugs-list

[issue5556] interactive interpreter, source encoding

2009-03-24 Thread Jean-Michel Fauth
New submission from Jean-Michel Fauth wxjmfa...@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