original ) (raw )Created on 2018-01-26 04:04 by dancollins34 , last changed 2022-04-11 14:58 by admin . This issue is now closed .
Pull Requests
URL
Status
Linked
Edit
PR 5535 dancollins34,2018-01-26 04:04
PR 5335 closed
dancollins34,2018-01-26 04:22
Messages (4)
msg310730 - (view) Author: (dancollins34) *
Date: 2018-01-26 04:04
To my knowledge, python currently has no capability to chain future execution, requiring another future to begin executing with the result from the first. I have submitted a pr to enable this functionality with a .then(self, fn) method on the concurrent.futures.Future object. -dancollins34
msg310731 - (view) Author: R. David Murray (r.david.murray) *
Date: 2018-01-26 04:09
I think this requires a discussion on the python-ideas mailing list, since API changes to Future need consideration in the asyncio context as well.
msg310733 - (view) Author: (dancollins34) *
Date: 2018-01-26 04:24
Okay, I'll post something.
msg317703 - (view) Author: Yury Selivanov (yselivanov) *
Date: 2018-05-25 19:37
Closing this one. I don't see us adding Future.then. Feel free to discuss on the MLs.
History
Date
User
Action
Args
2022-04-11 14:58:57
admin
set
github: 76853
2018-05-28 20:04:09
yselivanov
set
status: open -> closed
2018-05-25 19:37:59
yselivanov
set
nosy: + yselivanov , asvetlov messages: + components: + asyncio, - Library (Lib)resolution: rejectedstage: patch review -> resolved
2018-01-26 04:24:18
dancollins34
set
messages: +
2018-01-26 04:22:28
dancollins34
set
keywords: + patch stage: patch reviewpull_requests: + <pull%5Frequest5182>
2018-01-26 04:09:32
r.david.murray
set
versions: + Python 3.8, - Python 3.7nosy: + r.david.murray messages: + components: + Library (Lib), - Interpreter Coretype: enhancement
2018-01-26 04:04:25
dancollins34
create
