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 inglesp
Recipients Guido.van.Rossum, asvetlov, gvanrossum, inglesp, larry, pitrou, python-dev, tim.golden, tim.peters, vstinner
Date 2014-05-09.22:54:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399676051.48.0.0611735687072.issue21435@psf.upfronthosting.co.za>
In-reply-to
Content
It was actually through playing with aiohttp that I first hit this issue.  I think I originally hit the problem with something like:

import asyncio
import aiohttp

@asyncio.coroutine
def do_work(future):
    response = yield from aiohttp.request('get', 'http://google.com')
    future.set_result(None)

loop = asyncio.get_event_loop()
future = asyncio.Future()
asyncio.Task(do_work(future))
future.add_done_callback(print)
loop.run_forever()
History
Date User Action Args
2014-05-09 22:54:11inglespsetrecipients: + inglesp, gvanrossum, tim.peters, pitrou, vstinner, larry, tim.golden, asvetlov, python-dev, Guido.van.Rossum
2014-05-09 22:54:11inglespsetmessageid: <1399676051.48.0.0611735687072.issue21435@psf.upfronthosting.co.za>
2014-05-09 22:54:11inglesplinkissue21435 messages
2014-05-09 22:54:11inglespcreate