bpo-31641: Allow arbitrary iterables in concurrent.futures.as_completed()#3830
bpo-31641: Allow arbitrary iterables in concurrent.futures.as_completed()#3830ambv merged 1 commit into
concurrent.futures.as_completed()#3830Conversation
…ted()` This was possible before. pythonGH-1560 introduced a regression after 3.6.2 got released where only sequences were accepted now. This commit addresses this problem.
|
News entry not required because this reverts a regression before a release was made. |
Sorry, something went wrong.
|
@ned-deily This is a release blocker for 3.6.3, please make sure to merge it. We'll probably want RC2 because of this? |
Sorry, something went wrong.
pitrou
left a comment
There was a problem hiding this comment.
Thanks for noticing and for the quick fix!
Sorry, something went wrong.
|
Thanks @ambv for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6. |
Sorry, something went wrong.
…completed()` (pythonGH-3830) This was possible before. pythonGH-1560 introduced a regression after 3.6.2 got released where only sequences were accepted now. This commit addresses this problem. (cherry picked from commit 574562c)
|
Re: "We'll probably want [3.6.3] RC2 because of this?" We could and normally would but this change seems isolated enough and simple enough that, unless someone has a strong objection, I'm inclined to just cherry pick it into 3.6.3 final unless some other, more intrusive change comes along to trigger a second RC. |
Sorry, something went wrong.
…completed()` (pythonGH-3830) (python#3831) This was possible before. pythonGH-1560 introduced a regression after 3.6.2 got released where only sequences were accepted now. This commit addresses this problem. (cherry picked from commit 574562c)
This was possible before. GH-1560 introduced a regression after 3.6.2 got
released where only sequences were accepted now. This commit addresses this
problem.
https://bugs.python.org/issue31641