As it happens, a few months ago we did the same here. I have a traceback2.py module with the same api as traceback. Displaying local variables is optional through keyword arguments. I was also able to refactor the original significantly, making it much clearer. I've pasted it here: http://dpaste.com/151597/ Its currently in production use and has had some of the sharp edges worn off.
K > -----Original Message----- > From: python-dev-bounces+kristjan=ccpgames....@python.org > [mailto:python-dev-bounces+kristjan=ccpgames....@python.org] On Behalf > Of Antoine Pitrou > Sent: 28. janúar 2010 14:15 > To: python-dev@python.org > Subject: Re: [Python-Dev] Improved Traceback Module > > Le Thu, 28 Jan 2010 14:33:11 +0100, Benjamin Schweizer a écrit : > > > > I've updated the traceback.py module; my improved version dumps all > > local variabes from the stack trace, which helps in debugging rare > > problems. You can find details in my latest blog post here: > > > > As Facundo said it shouldn't replace the default output but it could be > enabled through e.g. an additional argument. > Would you be interested in reworking your code for this, and also add > tests to Lib/test_traceback.py? You can then post your patch on http:// > bugs.python.org > > Regards > > Antoine. > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python- > dev/kristjan%40ccpgames.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
