RETIRED, further work has moved to Debian project infrastructure
Go to file
Robert Collins 652c95d267 Handle objects with broken __unicode__
Because Python 2 objects may have __unicode__ broken, and we need
unicode output to avoid implicit decodes, explicitly handle
__unicode__.
2015-03-09 13:31:29 +13:00
traceback2 Handle objects with broken __unicode__ 2015-03-09 13:31:29 +13:00
.gitignore Supporting boilerplate. 2015-03-06 14:43:28 +13:00
.testr.conf Basic boilerplate. 2014-11-21 07:50:36 +13:00
AUTHORS Supporting boilerplate. 2015-03-06 14:43:28 +13:00
Makefile Supporting boilerplate. 2015-03-06 14:43:28 +13:00
README.rst Handle objects with broken __unicode__ 2015-03-09 13:31:29 +13:00
requirements.txt Time for 1.0.0. 2015-03-06 16:18:39 +13:00
setup.cfg Time for 1.0.0. 2015-03-06 16:18:39 +13:00
setup.py Basic boilerplate. 2014-11-21 07:50:36 +13:00
test-requirements.txt Port trunk traceback module to standalone w/3.5. 2014-11-21 09:58:04 +13:00

README.rst

A backport of traceback to older supported Pythons.

>>> import traceback2 as traceback

Profit.

Things to be aware of!

In Python 2.x, unlike traceback, traceback2 creates unicode output (because it depends on the linecache2 module).

Exception frame clearing silently does nothing if the interpreter in use does not support it.

traceback2._some_str, which while not an official API is so old its likely in use behaves similarly to the Python3 version - objects where unicode(obj) fails but str(object) works will be shown as b'thestrvaluerepr'.