[issue32672] .then execution of actions following a future's completion

Change by Yury Selivanov : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue32672] .then execution of actions following a future's completion

Yury Selivanov added the comment: Closing this one. I don't see us adding Future.then. Feel free to discuss on the MLs. -- components: +asyncio -Library (Lib) nosy: +asvetlov, yselivanov resolution: -> rejected stage: patch review -> resolved ___ P

[issue32672] .then execution of actions following a future's completion

dancollins34 added the comment: Okay, I'll post something. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32672] .then execution of actions following a future's completion

Change by dancollins34 : -- keywords: +patch pull_requests: +5182 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue32672] .then execution of actions following a future's completion

R. David Murray added the comment: 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. -- components: +Library (Lib) -Interpreter Core nosy: +r.david.murray type: -> enhancement versions: +

[issue32672] .then execution of actions following a future's completion

New submission from dancollins34 : 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.futur