➜

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, srkunze, vstinner, yselivanov
Date 2015-07-07.15:14:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436282092.44.0.0999089529466.issue24571@psf.upfronthosting.co.za>
In-reply-to
Content 
But that example also shows what's wrong with the idea. I presume load_remote_data_set1 and load_remote_data_set2 are themselves just using synchronous I/O, and the parallelization is done using threads. So why not use concurrent.futures? Why bother with asyncio at all?
History
Date User Action Args
2015-07-07 15:14:52gvanrossumsetrecipients: + gvanrossum, ncoghlan, pitrou, vstinner, giampaolo.rodola, yselivanov, srkunze
2015-07-07 15:14:52gvanrossumsetmessageid: <1436282092.44.0.0999089529466.issue24571@psf.upfronthosting.co.za>
2015-07-07 15:14:52gvanrossumlinkissue24571 messages
2015-07-07 15:14:52gvanrossumcreate