[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Change by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

miss-islington added the comment: New changeset 53374cc57f33f1afb22924da3a76ec6cf9e4afc1 by Miss Islington (bot) in branch '3.7': bpo-30579: Docs for dynamic traceback creation (GH-5653)

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Change by miss-islington : -- pull_requests: +5457 ___ Python tracker ___

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nick Coghlan added the comment: New changeset aec7532ed3ccbd29d3429a3f375e25f956c44003 by Nick Coghlan in branch 'master': bpo-30579: Docs for dynamic traceback creation (GH-5653) https://github.com/python/cpython/commit/aec7532ed3ccbd29d3429a3f375e25f956c44003

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Change by Nick Coghlan : -- pull_requests: +5455 ___ Python tracker ___ ___

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nick Coghlan added the comment: Thanks for the patch! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nick Coghlan added the comment: New changeset e46a8af450210ee5c7f0459ad6beddbc626ae60f by Nick Coghlan (Nathaniel J. Smith) in branch 'master': bpo-30579: Allow TracebackType creation and tb_next mutation from Python (GH-4793)

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nathaniel Smith added the comment: Ping -- anyone up for reviewing PR 4793? https://github.com/python/cpython/pull/4793 It's pretty straightforward, and I figure better to ping now and beat the end-of-month rush :-) -- ___ Python

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nathaniel Smith added the comment: PR 4793 provides everything that Jinja2 and Trio actually need right now. It doesn't provide any way to annotate tracebacks with extra data, but I'm not entirely sure if that's necessary or what it would look like, so I figured I'd at least

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Change by Giampaolo Rodola' : -- nosy: -giampaolo.rodola ___ Python tracker ___ ___

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Change by Nathaniel Smith : -- keywords: +patch pull_requests: +4692 stage: needs patch -> patch review ___ Python tracker ___

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Changes by Mariatta Wijaya : -- stage: -> needs patch ___ Python tracker ___ ___

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nick Coghlan added the comment: Aye, if you need full post-mortem debugging support, then updating the public API of the actual traceback objects based on the current ctypes-based workaround does seem like a better path forward. TracebackException and friends would more come into play for the

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nathaniel Smith added the comment: My understanding is that the major difference between a real traceback object and a TracebackException object is that the latter is specialized for printing, so it can be lighter weight (no pinning of frame objects in memory), but loses some utility (can't

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nick Coghlan added the comment: Rather than allowing this on tracebacks directly, I'd prefer to build on the "TracebackException" work and allow traceback summaries in all the places where we currently require real tracebacks (including exception __traceback__ attributes):

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

Nathaniel Smith added the comment: Uh, please ignore the random second paste of the jinja2 URL in the middle of the second to last paragraph. -- ___ Python tracker

[issue30579] Allow traceback objects to be instantiated/mutated/annotated

New submission from Nathaniel Smith: Currently, traceback objects don't expose any public constructor, are immutable, and don't have a __dict__ or allow subclassing, which makes it impossible to add extra annotations them. It would be nice if these limitations were lifted, because there are