[issue24195] Add `Executor.filter` to concurrent.futures
Nick Coghlan
report at bugs.python.org
Sat May 23 07:03:28 CEST 2015
Nick Coghlan added the comment:
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.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue24195>
_______________________________________
More information about the Python-bugs-list
mailing list