[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

R. David Murray added the comment: Doc patch applied in r71631. -- resolution: -> accepted stage: patch review -> committed/rejected status: open -> closed ___ Python tracker __

[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

Georg Brandl added the comment: Looks good to me. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

R. David Murray added the comment: As I said, if you replace the environment it is your responsibility to supply a working environment. I've attached a doc patch that adds a warning about this with the information that a valid SystemRoot is needed to run a side-by-side assembly (whatever that i

[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

Lenard Lindstrom added the comment: notepad.exe forms a side-by-side assembly with COMCTL32.DLL. So SystemRoot must be included in the environment. The following example works with Python 2.5.2 on Windows XP. === import struct, subproc

[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

Lenard Lindstrom added the comment: The notepad example works with Pythons 2.4.4 and 2.5.4 on Windows 98. So something changed in Windows XP. The 0xc0150004 error code crops up when a side-by-side assembly fails to load. The DLL loader appears to use the SystemRoot environment variable to find d

[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

Paul Morelle added the comment: I have just figured out that if you initialize env with os.environ.copy() and then add/modify its components, then the bug disappears: env = os.environ.copy() env['FOO'] = 'BAR' […] But I have no idea (for the moment) of which variable is mandatory or not.

[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

R. David Murray added the comment: If you are passing a custom environment to a subprocess, then you must supply everything in that environment that the program you are calling requires in order to run. That said, it would be a good idea to document the Windows minimum environment requirements

[issue3440] Starting any program as a subprocess fails when subprocess.Popen has env argument

Paul Morelle added the comment: Hello, I can reproduce the bug on a Windows XP Professional, SP 3, with three versions of Python: Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)] on win32 Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)] on win32