Created on 2010-06-05 02:39 by flashk, last changed 2010-06-23 18:19 by flashk.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| IgnoreWindowsRegistry_27.patch | flashk, 2010-06-05 02:39 | Patch for 2.7 | review | |
| IgnoreWindowsRegistry_32.patch | flashk, 2010-06-05 02:39 | Patch for 3.2 | review | |
| Messages (3) | |||
|---|---|---|---|
| msg107121 - (view) | Author: (flashk) | Date: 2010-06-05 02:39 | |
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 |
|||
| msg107244 - (view) | Author: Éric Araujo (eric.araujo) *  |
Date: 2010-06-06 22:23 | |
Looks good to me. Adding the release manager to the nosy list. |
|||
| msg108468 - (view) | Author: (flashk) | Date: 2010-06-23 18:19 | |
Any chance of getting this into 2.7 final? This fix is important for embedding Python in Windows applications. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-06-23 18:19:35 | flashk | set | messages: + msg108468 |
| 2010-06-06 22:23:42 | eric.araujo | set | keywords:
+ needs review nosy: + eric.araujo, benjamin.peterson messages: + msg107244 |
| 2010-06-05 02:39:45 | flashk | set | files: + IgnoreWindowsRegistry_32.patch |
| 2010-06-05 02:39:23 | flashk | create | |