[TIP] Annotated tracebacks

[Robert Collins]

On 19 October 2014 23:35, holger krekel <holger at merlinux.eu> wrote:

> I am not keen on including in stdlib first.  The place for things to be
> adopted by the community is PyPI these days.  Which also helps to heal the
> py2/py3 chasm.  It it's stable and used a lot it could go to stdlib later.
> Anyway, let's first get the design/requirements right (see also question
> above).  After that i can look at the code and suggest something.
> IIRC it has one abstraction layer more than is strictly needed
> which originated from PyPy needs which i am not sure are still actual.

Speaking of pypi:
https://pypi.python.org/pypi/diagnostics/0.2.4
https://pypi.python.org/pypi/tracebackturbo/0.1.2
  -  https://github.com/cxcv/python-tracebackturbo#sample-output
https://pypi.python.org/pypi/infi.traceback/0.3.10
https://pypi.python.org/pypi/xtraceback/0.4.0-rc1

You might like to eyeball these :)

I still want to get something into the stdlib so that Python's
upstream tests can have better output :)

-Rob



-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud