Thank you for the response. I had the digest mailing list option
activated so I couldn't respond to the mail directly. I hope it will
parse my response correctly. :)
I had already tried to copy the executable over to the new directory.
That didn't work. Additionally, another pexpect exception is raised
the when winpexpect cannot find the specified file:
Traceback (most recent call last):
File "testwinpexpect.py", line 8, in <module>
winpexpect.winspawn("plonk.exe")
File "C:\Python27\lib\site-packages\winpexpect-1.5-py2.7.egg\winpexpect.py", l
ine 346, in __init__
logfile=logfile, cwd=cwd, env=env)
File "C:\Python27\lib\site-packages\winpexpect-1.5-py2.7.egg\pexpect.py", line
429, in __init__
self._spawn (command, args)
File "C:\Python27\lib\site-packages\winpexpect-1.5-py2.7.egg\winpexpect.py", l
ine 369, in _spawn
raise ExceptionPexpect, 'Command not found: %s' % self.command
pexpect.ExceptionPexpect: Command not found: plonk.exe
I used a sysinternals tool similiar to strace in Linux to verify that
the executable actually opens the plink.exe file. So it's not related
to any path issues.
I should mention that the cx_freeze executable works on the same
computer I created it on. But when I move it to other computers it
fails. I'm starting to think this is related to some kind of DLL file
not being loaded correctly.
--
Med vänliga hälsningar / Kind regards,
William
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
cx-freeze-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
