[pypy-issue] [issue1508] PyPy 2.0 does not respect default encoding

Armin Rigo tracker at bugs.pypy.org
Sun Jun 2 16:04:01 CEST 2013


Armin Rigo <armin.rigo at gmail.com> added the comment:

Can you give more details?  This issue is messy because it depends on your
terminal, on your environment variables, and so on.  We can't tell on which
encoding what you type interactively is sent to the interpreter.

What would help is a file "x.py" that you attach to this bug report, such that
"python x.py" works and "pypy x.py" doesn't, as well as the output of "env" to
see which environment variables you have.  Also, I guess that in order to use
"setdefaultencoding()" you'd actually need "python -S" and "pypy -S" (i.e. don't
run site.py; the name sys.setdefaultencoding is normally killed by site.py).

----------
nosy: +arigo
status: unread -> chatting

________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue1508>
________________________________________


More information about the pypy-issue mailing list