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 Arfrever, benjamin.peterson, giampaolo.rodola, gvanrossum, ncoghlan, pitrou, python-dev, richard.kiss, vstinner, yselivanov
Date 2014-04-20.15:34:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398008061.06.0.160755513851.issue21209@psf.upfronthosting.co.za>
In-reply-to
Content
IMO the comment is too aggressive. I want the workaround to stay in the codebase so CPython asyncio ans Tulip asyncio (== upstream) don't diverge.
History
Date User Action Args
2014-04-20 15:34:21gvanrossumsetrecipients: + gvanrossum, ncoghlan, pitrou, vstinner, giampaolo.rodola, benjamin.peterson, Arfrever, python-dev, yselivanov, richard.kiss
2014-04-20 15:34:21gvanrossumsetmessageid: <1398008061.06.0.160755513851.issue21209@psf.upfronthosting.co.za>
2014-04-20 15:34:21gvanrossumlinkissue21209 messages
2014-04-20 15:34:20gvanrossumcreate