This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients Daniel.Goertzen, amaury.forgeotdarc, atuining, belopolsky, eric.araujo, flox, grahamd, pitrou, python-dev, vstinner
Date 2011-11-15.13:06:55
SpamBayes Score 0.0030705822
Marked as misclassified No
Message-id <1321362416.69.0.507136691814.issue6501@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2011-11-15 13:06:56eric.araujosetrecipients: + eric.araujo, amaury.forgeotdarc, atuining, belopolsky, pitrou, vstinner, grahamd, flox, Daniel.Goertzen, python-dev
2011-11-15 13:06:56eric.araujosetmessageid: <1321362416.69.0.507136691814.issue6501@psf.upfronthosting.co.za>
2011-11-15 13:06:56eric.araujolinkissue6501 messages
2011-11-15 13:06:55eric.araujocreate