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 glangford, gvanrossum, mark.dickinson, tim.peters, vstinner
Date 2014-01-23.15:47:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390492058.14.0.607884476759.issue20367@psf.upfronthosting.co.za>
In-reply-to
Content
I think you the caller was wrong to pass in [f, f] in the first place.

In asyncio, the argument is converted into a set before using it, but there's still a bug if you pass it a list containing two references to the same coroutine -- it gets wrapped in two separate Futures. I think the better behavior is to convert to a set first and then map coroutines to Futures.

So concurrent.futures should also convert to a set first.
History
Date User Action Args
2014-01-23 15:47:38gvanrossumsetrecipients: + gvanrossum, tim.peters, mark.dickinson, vstinner, glangford
2014-01-23 15:47:38gvanrossumsetmessageid: <1390492058.14.0.607884476759.issue20367@psf.upfronthosting.co.za>
2014-01-23 15:47:38gvanrossumlinkissue20367 messages
2014-01-23 15:47:37gvanrossumcreate