[Wow, it's Mark! <wink>] >> The binary version did produce a log file, but not the souce code >> one. > > If I recall correctly, the source code version writes all output to > Pythonwin's "Trace Collector Debugging Tool" (from the "Tools" menu). > Alternatively, execute the > \python23\lib\site-packages\win32\lib\win32traceutil.py script in > another > Command Prompt window. Once you have done either of these you > should see > the trace messages for the source code version. I suspect you will > see a > traceback when clicking on the folder once you get this working.
You do recall correctly; this is how logging works for the Outlook plug-in. > There is actually no good reason for this - it was just my > preference while > I was working on the plugin. It would probably be less confusing > if both > source and binary logged the same way. :) The source still has comments about switching to a "proper" logging system some day. It might be just that it's what I'm used to, but I prefer finding the 'log' in the trace collector to log files while I'm working on things (admittedly, not often these days), just as I prefer that sb_server.py outputs to stdout if run in a console rather than to the log files it otherwise uses. If you want a 'good' reason, then the best I can think of is that it's quicker to open the trace collector (assuming that one is working in PythonWin) than navigate all the way to the data directory. =Tony.Meyer _______________________________________________ [email protected] http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
