<br><br>
<div><span class="gmail_quote">On 10/7/05, <b class="gmail_sendername">Dennis Allison</b> <<a href="mailto:allison@shasta.stanford.edu">allison@shasta.stanford.edu</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>Depends upon what you want to do and how much access you have. For<br>debugging purposes I often use an external procedure
<br><br>def debugWindow( data ):<br> fd = open('/tmp/debugWindow",'a')<br> fd.write( str(data))<br> fd.close()<br><br>and look at the output with<br><br> tail -f /tmp/debugWindow<br><br>Or, you can use the same approach to write to syslog using the Python
<br>logging module<br><br>Or you can piggyback into the Zope logging mechanism--see the sources for<br>that exercise.<br><br>I find the external procedure approach to be useful in its simplicity</blockquote>
<div> </div>
<div>OK -- thanks to those that replied (many with a similar solution).</div>
<div> </div>
<div>I do have access to the server (Win2000 in my case) so I can pretty well do anything I want.</div>
<div> </div>
<div>It comes back now -- I did something like that but then called it through a gateway Python script that allowed me to turn off all logging in one spot easily (by modifying the script) in case I wanted to leave the debug statements there temporarily and not incur the expense of a huge log file.
</div><br> </div>