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 giampaolo.rodola, gvanrossum, ncoghlan, pitrou, python-dev, richard.kiss, vstinner, yselivanov
Date 2014-04-14.14:48:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
This is nice (a backport 3.3 would be even nicer) but at least for the PyPI
repo version of Tulip I'd like to have work-around so people won't run into
this when they are using a slightly outdated Python version. I'll think
about which of my work-arounds is safe for that while not breaking the
intended functionality of CoroWrapper (i.e. that it prints a warning when
destructed before it has reached the end). That may require setting an
additional flag.
Date User Action Args
2014-04-14 14:48:21gvanrossumsetrecipients: + gvanrossum, ncoghlan, pitrou, vstinner, giampaolo.rodola, python-dev, yselivanov, richard.kiss
2014-04-14 14:48:21gvanrossumlinkissue21209 messages
2014-04-14 14:48:21gvanrossumcreate