Sven Ingebrigt Ulland wrote: >Hello there. How would I go about debugging mailman, by -- >for example -- polluting the .py libraries with print or >assert statements? If I do that (which seems like a pretty >thoughtless idea), the output would end up .. in /dev/null? >It would probably be better to write to file in stead? > <snip> > >I'd really like to debug that code passage to verify what >variables are screwed up, and which are not. > >Any tips?
Output to stderr from the queue runners (the running Mailman processes) is copied to Mailman's error log so you can print to sys.stderr and the output goes to the error log. You can also use Mailman.Logging.Syslog.syslog() calls to write to a 'debug' or other log (which will be created if necessary). -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
