[issue5556] interactive interpreter, source encoding

Terry J. Reedy 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 source string

[issue5556] interactive interpreter, source encoding

R. David Murray 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: -> invalid stage: unit

[issue5556] interactive interpreter, source encoding

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5556] interactive interpreter, source encoding

Amaury Forgeot d'Arc 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

Changes by Mark Lawrence : -- nosy: +amaury.forgeotdarc stage: -> unit test needed versions: +Python 2.7, Python 3.1, Python 3.2 -Python 3.0 ___ Python tracker ___ __

[issue5556] interactive interpreter, source encoding

New submission from Jean-Michel Fauth : 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 bump