[issue32679] concurrent.futures should store full sys.exc_info()

Irit Katriel added the comment: Following the changes in issue45711, exc_info[2] is exactly the same as exc_info[1].__traceback__, so there is no point in making this change now. -- resolution: -> not a bug stage: -> resolved status: open -> closed

[issue32679] concurrent.futures should store full sys.exc_info()

Irit Katriel added the comment: 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? -- nosy: +iritkatriel

[issue32679] concurrent.futures should store full sys.exc_info()

Brian Quinlan added the comment: 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. -- ___ Python tracker

[issue32679] concurrent.futures should store full sys.exc_info()

Change by Cheryl Sabella : -- nosy: +bquinlan, pitrou versions: -Python 3.4, Python 3.5, Python 3.6 ___ Python tracker ___ ___

[issue32679] concurrent.futures should store full sys.exc_info()

Jonas H. added the comment: See also https://stackoverflow.com/questions/19309514/getting-original-line-number-for-exception-in-concurrent-futures for other people having the same problem -- ___ Python tracker

[issue32679] concurrent.futures should store full sys.exc_info()

New submission from Jonas H. : 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