Is that all your 'except' clause does? Because if so, you're not going to get any tracebacks at all, because the expect is catching them all and doing nothing with them. Try removing the try..except. seb * Jean Jordaan <jean@upfrontsystems.co.za> [010907 11:44]:
Hi all
We've been successfully using this code from an external method to run a third-party program, but it's mysteriously stopped working::
try: child_stdout, \ child_stdin, \ child_stderr = popen3('/usr/local/zope/creme/2-3-0/Extensions/passfeko /usr/local/zope/creme/2-3-0/Extensions/passfeko.xml') success.append("'passfeko' executed.\n") #DBG except: exception = sys.exc_info() errors.append( "Could not execute 'passfeko'" \ + '\n --' + str(exception[0]) \ + '\n --' + str(exception[1]) \ + '\n --' + str(exception[2]) \ ) # TODO: display the traceback.
The third-party program, 'passfeko', writes a textfile, taking the 'passfeko.xml' file as input. If I run::
./passfeko passfeko.xml
from the commandline, the textfile is flawlessly created.
When run from Zope, no exception is raised, but no textfile is created.
Any ideas?
Jean
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )