➜

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 glangford
Recipients glangford
Date 2014-01-23.15:00:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390489248.24.0.751917808957.issue20367@psf.upfronthosting.co.za>
In-reply-to
Content 
concurrent.futures.as_completed([f,f]) will yield f twice, then fail with a KeyError for a Future f which is not completed.

If the Future has already completed, as_completed([f,f]) will yield f once and does not trigger an exception.

What is the correct behaviour?
   as_completed( [f,f] ) -> yield f twice ?
   wait( [f,f], return_when=ALL_COMPLETED ) -> yield f twice ?
History
Date User Action Args
2014-01-23 15:00:48glangfordsetrecipients: + glangford
2014-01-23 15:00:48glangfordsetmessageid: <1390489248.24.0.751917808957.issue20367@psf.upfronthosting.co.za>
2014-01-23 15:00:48glangfordlinkissue20367 messages
2014-01-23 15:00:47glangfordcreate