[issue6501] Fatal error on startup with invalid PYTHONIOENCODING
Éric Araujo
report at bugs.python.org
Tue Nov 15 14:06:56 CET 2011
Éric Araujo <merwok at netwok.org> added the comment:
> Currently different environment variables are treated differently. For example,
> mistakes in PYTHONHOME and PYTHONIOENCODING cause fatal error while an error in
> PYTHONSTARTUP is reported but does not terminate python:
If PYTHONSTARTUP is the only envvar with non-fatal errors, I think it’s okay. PYTHONHOME contains vital information, PYTHONIOENCODING is set by the programmer/admin and their code probably depends on it, but PYTHONSTARTUP is just niceties for the interactive interpreter, so non-vital IMO.
----------
nosy: +eric.araujo
versions: +Python 2.7, Python 3.3 -Python 3.1
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue6501>
_______________________________________
More information about the Python-bugs-list
mailing list