Skip to content

bpo-31641: Allow arbitrary iterables in concurrent.futures.as_completed() #3830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 29, 2017

Conversation

ambv
Copy link
Contributor

@ambv ambv commented Sep 29, 2017

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

…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.
@ambv
Copy link
Contributor Author

ambv commented Sep 29, 2017

News entry not required because this reverts a regression before a release was made.

@ambv ambv requested review from ned-deily and pitrou September 29, 2017 21:20
@ambv
Copy link
Contributor Author

ambv commented Sep 29, 2017

@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?

Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for noticing and for the quick fix!

@ambv ambv merged commit 574562c into python:master Sep 29, 2017
@miss-islington
Copy link
Contributor

Thanks @ambv for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6.
🐍🍒⛏🤖

@bedevere-bot
Copy link

GH-3831 is a backport of this pull request to the 3.6 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 29, 2017
…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)
@ambv ambv deleted the whyLenTho branch September 29, 2017 21:34
ambv pushed a commit that referenced this pull request Sep 29, 2017
…completed()` (GH-3830) (#3831)

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.
(cherry picked from commit 574562c)
Copy link
Member

@ned-deily ned-deily left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ned-deily
Copy link
Member

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.

ned-deily pushed a commit to ned-deily/cpython that referenced this pull request Oct 3, 2017
…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)
dalcinl added a commit to dalcinl/pythonfutures that referenced this pull request Oct 3, 2017
agronholm pushed a commit to agronholm/pythonfutures that referenced this pull request Nov 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip news type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants