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 ncoghlan
Recipients bquinlan, cool-RR, ethan.furman, jnoller, ncoghlan, paul.moore, pitrou, sbt
Date 2015-05-23.05:03:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I vary between +0 and -0 for the addition of the concrete method.

When I'm at +0, the main rationale is that we *don't* have the "Where do we stop?" risk here that itertools faces, as we're just replicating the synchronous builtins.

When I'm at -0, the main rationale is that a recipe works with *any* version of Python that provides concurrent.futures (including any version of the PyPI backport), and is hence useful immediately, while a method would only work the version where we added it.
Date User Action Args
2015-05-23 05:03:28ncoghlansetrecipients: + ncoghlan, paul.moore, bquinlan, pitrou, jnoller, cool-RR, ethan.furman, sbt
2015-05-23 05:03:28ncoghlansetmessageid: <>
2015-05-23 05:03:28ncoghlanlinkissue24195 messages
2015-05-23 05:03:27ncoghlancreate