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 flashk
Recipients flashk
Date 2010-06-05.02:39:22
SpamBayes Score 9.331304e-06
Marked as misclassified No
Message-id <1275705565.03.0.753930892849.issue8901@psf.upfronthosting.co.za>
In-reply-to
Content
Hi,

I noticed that Python still uses the Windows registry to initialize sys.path, when the -E option is used.

From my understanding, this option is mostly used by programs that are running an embedded version of python, and don't want it to be affected by global installations. Ignoring the registry, along with environment variables, seems to be the correct behavior in this case.

I asked about this on the python-dev list (http://mail.python.org/pipermail/python-dev/2010-June/100492.html) and was told to submit a patch for this if I wanted it fixed before the 2.7 release.

I've included a patch for 2.7 and 3.2
History
Date User Action Args
2010-06-05 02:39:25flashksetrecipients: + flashk
2010-06-05 02:39:25flashksetmessageid: <1275705565.03.0.753930892849.issue8901@psf.upfronthosting.co.za>
2010-06-05 02:39:23flashklinkissue8901 messages
2010-06-05 02:39:22flashkcreate