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 gvanrossum
Recipients benjamin.peterson, giampaolo.rodola, gvanrossum, ncoghlan, pitrou, python-dev, richard.kiss, vstinner, yselivanov
Date 2014-04-15.01:19:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397524766.86.0.894076633951.issue21209@psf.upfronthosting.co.za>
In-reply-to
Content
OK, looks good. I tried your test with my earlier workaround and the wrapper got deallocated too early, proving that my workaround was indeed wrong and your test is useful. I am still concerned theoretically that the CoroWrapper.send() signature is different from a real generator's send() method, but I think that send() to a coroutine is an internal detail anyway, so I can live with that, and I don't see another work-around.

When you commit, can you do upstgream (Tulip) first?
History
Date User Action Args
2014-04-15 01:19:26gvanrossumsetrecipients: + gvanrossum, ncoghlan, pitrou, vstinner, giampaolo.rodola, benjamin.peterson, python-dev, yselivanov, richard.kiss
2014-04-15 01:19:26gvanrossumsetmessageid: <1397524766.86.0.894076633951.issue21209@psf.upfronthosting.co.za>
2014-04-15 01:19:26gvanrossumlinkissue21209 messages
2014-04-15 01:19:26gvanrossumcreate