Hi, On Thu, Sep 28, 2006 at 10:55:14AM +0200, 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? > > Right now I'm having a specific problem, but it would be > nice to have some general debugging methods to use in the > future for other problems. <snip> > I'd really like to debug that code passage to verify what > variables are screwed up, and which are not. > > Any tips?
Perhaps the section "DEBUGGING LIVE MAILMAN" in http://non-gnu.uvt.nl/repos/mailman-ssls/mailman-ssls/doc/secure-list-patch.pod is of any use. Bye, Joost -- Joost van Baal http://abramowitz.uvt.nl/ Tilburg University [EMAIL PROTECTED] The Netherlands
signature.asc
Description: Digital signature
_______________________________________________ Mailman-Developers mailing list [email protected] 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
