subprocess only good for win32?
in [Python]
|
Prev: Question about list comprehension/standard "for" disparities
Next: Get Eclipse/PyDev to run scripts that don't end in .py
From: wukong on 1 Apr 2010 12:35 On Mar 31, 3:47 pm, "Martin v. Loewis" <mar...(a)v.loewis.de> wrote: > > WindowsError: [Error 14001] The application has failed to start > > because its side-by-side configuration is incorrect. Please see the > > application event log for more detail > > This is a configuration error on your system. The application you are > trying to start is incorrectly installed - it's not only that Python > can't start it, but nobody can. > > Regards, > Martin but python runs happy otherwise, only this call to subprocess resulted in an err. does anyone know for sure subprocess runs on win64? or any others like, popen does? thanks wk
From: wukong on 1 Apr 2010 12:36 On Mar 31, 3:47 pm, "Martin v. Loewis" <mar...(a)v.loewis.de> wrote: > > WindowsError: [Error 14001] The application has failed to start > > because its side-by-side configuration is incorrect. Please see the > > application event log for more detail > > This is a configuration error on your system. The application you are > trying to start is incorrectly installed - it's not only that Python > can't start it, but nobody can. > > Regards, > Martin nad also as i mentioned previously, it runs great on win32.
From: Steve Holden on 1 Apr 2010 12:58 wukong wrote: > On Mar 31, 3:47 pm, "Martin v. Loewis" <mar...(a)v.loewis.de> wrote: >>> WindowsError: [Error 14001] The application has failed to start >>> because its side-by-side configuration is incorrect. Please see the >>> application event log for more detail >> This is a configuration error on your system. The application you are >> trying to start is incorrectly installed - it's not only that Python >> can't start it, but nobody can. >> >> Regards, >> Martin > > but python runs happy otherwise, only this call to subprocess resulted > in an err. does anyone know for sure subprocess runs on win64? or > any others like, popen does? > thanks > wk Subprocess runs another program. It's the program you are running that's giving the error, Python is merely reporting it. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 See PyCon Talks from Atlanta 2010 http://pycon.blip.tv/ Holden Web LLC http://www.holdenweb.com/ UPCOMING EVENTS: http://holdenweb.eventbrite.com/
From: Michel Claveau - MVP on 1 Apr 2010 13:11 Hi! > side-by-side configuration is incorrect Others have given you an explanation. A possibility: you use a DLL directly, without having installed. That is OK with some DLL, and no OK with others DLL. @-salutations -- Michel Claveau
From: Piet van Oostrum on 1 Apr 2010 16:55
>>>>> wukong <novacompute(a)gmail.com> (w) wrote: >w> also subprocess.py clearly says >w> """ >w> import sys >w> mswindows = (sys.platform == "win32") >w> """ It may sound strange, but even in 64-bit Python on Win64, sys.plattform=="win32". You can check that subprocess is working, e.g. with subprocess.call('dir', shell=True) -- Piet van Oostrum <piet(a)vanoostrum.org> WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4] Nu Fair Trade woonwaar op http://www.zylja.com |