Message323703
asyncio.future.wrap_future is used to wrap a concurrent.future.Future in a asyncio.future.Future.
The actual implementation as the following behaviours :
1) When the concurrent.future.Future gets a result, the asyncio.future.Future gets the same result,
2) When the asyncio.future.Future is cancelled, the concurrent.future.Future is cancelled
I wonder why the futures synchronisation is not symmetrical ?
I propose to add the following behaviours :
3) When the asyncio.future.Future gets a result, the concurrent.future.Future gets the same result,
4) When the concurrent.future.Future is cancelled, the asyncio.future.Future is cancelled
I have also posted a request pull that implements the proposed behaviours, in case of acceptation.
If there is good reasons to not implement the proposed behaviours, I would be glad to know.
Thank you ! |
|
Date |
User |
Action |
Args |
2018-08-18 11:02:20 | huji | set | recipients:
+ huji, asvetlov, yselivanov |
2018-08-18 11:02:20 | huji | set | messageid: <1534590140.17.0.56676864532.issue34430@psf.upfronthosting.co.za> |
2018-08-18 11:02:20 | huji | link | issue34430 messages |
2018-08-18 11:02:19 | huji | create | |
|