[issue45924] Incorrect traceback when future's exception is raised multiple times

Change by lilydjwg : -- nosy: +lilydjwg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue45924] Incorrect traceback when future's exception is raised multiple times

Irit Katriel added the comment: Closed issue42682 as duplicate of this. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45924] Incorrect traceback when future's exception is raised multiple times

Irit Katriel added the comment: Closed issue46954 as a duplicate of this. -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue45924] Incorrect traceback when future's exception is raised multiple times

Change by Kumar Aditya : -- keywords: +patch nosy: +kumaraditya303 nosy_count: 5.0 -> 6.0 pull_requests: +28489 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30274 ___ Python tracker

[issue45924] Incorrect traceback when future's exception is raised multiple times

Vishal Pandey added the comment: thanks, It was my mistake, bug reproduced. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue45924] Incorrect traceback when future's exception is raised multiple times

Irit Katriel added the comment: Vishal, your output shows you’re running 3.8, not 3.10. traceback.print_exception() used to require 3 parameters, now it can make do with just one. See the docs for the details. -- ___ Python tracker

[issue45924] Incorrect traceback when future's exception is raised multiple times

Vishal Pandey added the comment: hey Irit, Is this issue platform-dependent? I am on ubuntu 20.04, and running python 3.10. I am not getting the same error that you have mentioned below. This is what I am getting. ### hello ... Traceback (most recent call last)

[issue45924] Incorrect traceback when future's exception is raised multiple times

Guido van Rossum added the comment: There's a similar issue with concurrent.futures.Future, and really, anything that stores exceptions and later raises them can get in trouble if there's a way to get the exception raised multiple times. This is rarely noticed because usually the exception i

[issue45924] Incorrect traceback when future's exception is raised multiple times

Change by Irit Katriel : -- pull_requests: -28067 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue45924] Incorrect traceback when future's exception is raised multiple times

Change by Irit Katriel : -- keywords: +patch pull_requests: +28067 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29780 ___ Python tracker ___ ___

[issue45924] Incorrect traceback when future's exception is raised multiple times

New submission from Irit Katriel : Background: https://github.com/python/cpython/pull/29780#issuecomment-981170548 https://github.com/python/cpython/pull/29780#issuecomment-981260365 ## import asyncio, traceback async def raise_after(fut, d