concurrent.futures should store full sys.exc_info()

[jonashaag]

BPO	32679
Nosy	@brianquinlan, @pitrou, @jonashaag, @iritkatriel

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2022-01-10.19:04:18.421>
created_at = <Date 2018-01-26.14:23:29.955>
labels = ['3.7', '3.8', 'type-feature', 'library', 'invalid']
title = 'concurrent.futures should store full sys.exc_info()'
updated_at = <Date 2022-01-10.19:04:18.420>
user = 'https://github.com/jonashaag'

bugs.python.org fields:

activity = <Date 2022-01-10.19:04:18.420>
actor = 'iritkatriel'
assignee = 'none'
closed = True
closed_date = <Date 2022-01-10.19:04:18.421>
closer = 'iritkatriel'
components = ['Library (Lib)']
creation = <Date 2018-01-26.14:23:29.955>
creator = 'jonash'
dependencies = []
files = []
hgrepos = []
issue_num = 32679
keywords = []
message_count = 5.0
messages = ['310762', '310763', '341982', '406064', '410244']
nosy_count = 4.0
nosy_names = ['bquinlan', 'pitrou', 'jonash', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32679'
versions = ['Python 3.7', 'Python 3.8']

[jonashaag]

Use case: Try to get a future's result using concurrent.futures.Future.result(), and log the full exception if there was any.

Currently, only "excinst" (sys.exc_info()[1]) is provided with the Future.exception() method.

Proposal: Add new Future.exc_info() method that returns the full sys.exc_info() at the time of the exception.

[jonashaag]

See also https://stackoverflow.com/questions/19309514/getting-original-line-number-for-exception-in-concurrent-futures for other people having the same problem

[brianquinlan]

My understanding is that tracebacks have a pretty large memory profile so I'd rather not keep them alive. Correct me if I'm wrong about that.

[iritkatriel]

The SO link seems to refer to Python 2, but on this issue the version are Python 3. In Python 3 the traceback is accessible from the exception via its __traceback__ attribute. Does that not give you what you need?

[iritkatriel]

Following the changes in bpo-45711, exc_info[2] is exactly the same as exc_info[1].__traceback__, so there is no point in making this change now.