subprocess only good for win32?

W

wukong

subprocess works fine on my win pro 32-bit, but not on vista 64-bit.
am i doing some wrong, or it just won't work for win64? If that's
true, will it be extended to win64 in teh future?
thanks in advance
wk
 
C

Chris Rebert

subprocess works fine on my win pro 32-bit, but not on vista 64-bit.
am i doing some wrong, or it just won't work for win64?  If that's
true, will it be extended to win64 in teh future?

Please characterize exactly how it is not working for you.
Include any error message and/or exception traceback.

Cheers,
Chris
 
W

wukong

Please characterize exactly how it is not working for you.
Include any error message and/or exception traceback.

Cheers,
Chris
--http://blog.rebertia.com

thanks for checking in, here's the error msg.
"""
Traceback (most recent call last):
File "C:/GUI/mainFunc.py", line 230, in OnSolve
subprocess.call([filename])
File "C:\Program Files (x86)\python26\lib\subprocess.py", line 470,
in call
return Popen(*popenargs, **kwargs).wait()
File "C:\Program Files (x86)\python26\lib\subprocess.py", line 621,
in __init__
errread, errwrite)
File "C:\Program Files (x86)\python26\lib\subprocess.py", line 830,
in _execute_child
startupinfo)
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
"""

also subprocess.py clearly says
"""
import sys
mswindows = (sys.platform == "win32")
"""

thanks
wk
 
T

Terry Reedy

subprocess works fine on my win pro 32-bit, but not on vista 64-bit.

You are more likely to get a helpful answer if you give a minimal
example and explain exactly what 'not [works fine]' means. What did
happen? Include full error traceback if there was one.
 
M

Martin v. Loewis

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
 
W

wukong

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
 
W

wukong

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.
 
S

Steve Holden

wukong said:
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
 
M

Michel Claveau - MVP

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
 
P

Piet van Oostrum

wukong said:
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)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,766
Messages
2,569,569
Members
45,042
Latest member
icassiem

Latest Threads

Top