Re: embedded python and interpreter threads

Woohoo, fixed my problem. It had to do with the way I was handling the methods which overwrote stderr and stdout. Yeehaw! =Charlie Charlie DeTar wrote: Quick correction, sorry - the command should read like this (I had omitted the "log" before 'CaptureStdout' and &#x

Re: embedded python and interpreter threads

s StdoutCatcher:\n" "\tdef write(self, str):\n" "\t\tlog.CaptureStdout(str)\n" "class StderrCatcher:\n" "\tdef write(self, str):\n" "\t\tlog.CaptureStderr(str)\n" "sys.stdout =

embedded python and interpreter threads

d explicitly 'stdout' and 'stderr'. I thought of the possibility that the 'logMethods' structure which includes my versions of stdout and stderr might be behaving statically. But I didn't define it as static... I am new to C, so there might be something basic I am missing. Any suggestions or ideas? Thanks, Charlie DeTar -- http://mail.python.org/mailman/listinfo/python-list