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 yselivanov
Recipients chris.jerdonek, giampaolo.rodola, mbussonn, ncoghlan, njs, yselivanov
Date 2017-12-13.17:32:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513186324.43.0.213398074469.issue30491@psf.upfronthosting.co.za>
In-reply-to
Content
>   send_ping() # don't care about result, forgot await
>   # get collected
>   await something_that_will_trigger_check_coros_weakreaf() # oh no !

I don't understand what you are trying to say with this example.  What is "something_that_will_trigger_check_coros_weakreaf" supposed to do?

The point of my proposal that you will have a coroutine reported at the "get collected" point in CPython, or sometime later in PyPy.

> So if its weak-refd then you can't be sure you are actually preventing non-awaited coros.

Sorry, I don't understand this sentence either.
History
Date User Action Args
2017-12-13 17:32:04yselivanovsetrecipients: + yselivanov, ncoghlan, giampaolo.rodola, njs, chris.jerdonek, mbussonn
2017-12-13 17:32:04yselivanovsetmessageid: <1513186324.43.0.213398074469.issue30491@psf.upfronthosting.co.za>
2017-12-13 17:32:04yselivanovlinkissue30491 messages
2017-12-13 17:32:04yselivanovcreate