This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jhaydaman
Recipients asvetlov, jhaydaman, yselivanov
Date 2018-04-06.18:15:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523038552.58.0.682650639539.issue33238@psf.upfronthosting.co.za>
In-reply-to
Content
May also be worth pointing out that even in the case of only calling set_result once, _done_callbacks still has _chain_future in it:


import asyncio
import concurrent.futures


f = concurrent.futures.Future()
async_f = asyncio.wrap_future(f)

f.set_result(1)
loop = asyncio.get_event_loop()
print(loop.run_until_complete(async_f))
print(f._done_callbacks)


>>> 1
>>> [<function _chain_future.<locals>._call_set_state at 0x7f1687f3c620>]


Should that be cleared by that point?
History
Date User Action Args
2018-04-06 18:15:52jhaydamansetrecipients: + jhaydaman, asvetlov, yselivanov
2018-04-06 18:15:52jhaydamansetmessageid: <1523038552.58.0.682650639539.issue33238@psf.upfronthosting.co.za>
2018-04-06 18:15:52jhaydamanlinkissue33238 messages
2018-04-06 18:15:52jhaydamancreate