[issue37281] asyncio Task._fut_waiter done callback

Валентин Бурченя added the comment: Thanks -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue37281] asyncio Task._fut_waiter done callback

Andrew Svetlov added the comment: See bpo-32363 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue37281] asyncio Task._fut_waiter done callback

Валентин Бурченя added the comment: Sorry, you right! But why not set_result and set_exception? My code: waiter_task.add_done_callback(lambda f: f.result()) because i don't wont to store my running tasks in the array but i must query awaiteable for the result. Thank you for a reply. -

[issue37281] asyncio Task._fut_waiter done callback

Andrew Svetlov added the comment: 1. Task._fut_waiter is a private API, please avoid it 2. Task class is derived from Future, thus it HAS add_done_callback() method. The other question is that from my experience if the application-level code uses add_done_callback() the design is not perfect

[issue37281] asyncio Task._fut_waiter done callback

Change by Karthikeyan Singaravelan : -- components: +asyncio nosy: +asvetlov, yselivanov ___ Python tracker ___ ___ Python-bugs-list

[issue37281] asyncio Task._fut_waiter done callback

New submission from Валентин Бурченя : Future has a done_callback, but Task not, why ? Is a safe to use Task._fut_waiter future done_callback? -- messages: 345575 nosy: Валентин Бурченя priority: normal severity: normal status: open title: asyncio Task._fut_waiter done callback type: beh