<br><br><div class="gmail_quote">On Mon, Jun 29, 2009 at 12:17 PM, Gertjan Klein <span dir="ltr"><<a href="mailto:gklein@xs4all.nl">gklein@xs4all.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tim Roberts wrote:<br>
<div class="im"><br>
>Gertjan Klein wrote:<br>
</div><div class="im">
>> 2) I see print statements in the source code, but I have no idea where<br>
>> they go; I checked the event log, but they are not there. Are they<br>
>> logged anywhere? If not, why are they there to begin with?<br>
>><br>
>> Any other tip on how to effectively debug this stuff would be most<br>
>> welcome as well.<br>
><br>
>The print statements go into empty space because there is no stdout for<br>
>that process. You can try using the logging module to log to a file, or<br>
>you can use ctypes to write to kernel32.OutputDebugString and using a<br>
>kernel debug log monitor to read them.<br>
<br>
</div>The logging module reminds me of Java too much. :( I think I'll try to<br>
write to a file, I have no idea if I have a kernel debug log monitor.<br>
<br>
<div><div class="h5">
<a href="http://mail.python.org/mailman/listinfo/python-win32" target="_blank"></a></div></div></blockquote><div><br>sys.stdout works like a normal Python file, so you should be able to assign a new file object to it.<br>
<br></div></div>You might try something like:<br>--------------<br>>>> x = open('x.txt','w')<br>>>> import sys<br>>>> sys.stdout = x<br>>>> print 'hello, world'<br>
>>> exit()<br><br>C:\Users\vernon>type x.txt<br>hello, world<br>-----------<br>For debugging, you may want to add <br>sys.stderr = x<br>as well.<br>--<br>Vernon Cole<br><br><br>