[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-10-03 Thread Ned Deily
Ned Deily added the comment: Cherry picked into 3.6.3 final -> closing -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ __

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-10-03 Thread Ned Deily
Change by Ned Deily : -- priority: release blocker -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-10-03 Thread Ned Deily
Ned Deily added the comment: New changeset 2e3fd03796528a9f88f79d38e1d890af153c8e61 by Ned Deily (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31641: Allow arbitrary iterables in `concurrent.futures.as_completed()` (GH-3830) (#3831) https://github.com/python/cpython/commit/2e3fd03796528a9

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Łukasz Langa
Łukasz Langa added the comment: Fix is already landed in 3.6 and master. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Łukasz Langa
Łukasz Langa added the comment: New changeset 9ef28b6ad3d5aff767e3d852499def8b5ae5ff5d by Łukasz Langa (Miss Islington (bot)) in branch '3.6': [3.6] bpo-31641: Allow arbitrary iterables in `concurrent.futures.as_completed()` (GH-3830) (#3831) https://github.com/python/cpython/commit/9ef28b6ad

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Roundup Robot
Change by Roundup Robot : -- pull_requests: +3814 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Łukasz Langa
Łukasz Langa added the comment: New changeset 574562c5ddb2f0429aab9af762442e6f9a3f26ab by Łukasz Langa in branch 'master': bpo-31641: Allow arbitrary iterables in `concurrent.futures.as_completed()` (#3830) https://github.com/python/cpython/commit/574562c5ddb2f0429aab9af762442e6f9a3f26ab --

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Łukasz Langa
Change by Łukasz Langa : -- keywords: +patch pull_requests: +3813 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Ned Deily
Ned Deily added the comment: Sounds like we need to get this fixed for 3.6.3 final which is scheduled for Monday (3 days). Or revert the previous fix. -- ___ Python tracker _

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Łukasz Langa
Change by Łukasz Langa : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue31641] concurrent.futures.as_completed() no longer accepts arbitrary iterables

2017-09-29 Thread Łukasz Langa
New submission from Łukasz Langa : bpo-27144 introduced a regression for `as_completed()`: it used to accept arbitrary iterables but now requires sequences, otherwise raising an exception like: Traceback (most recent call last): File "sandcastle/worker/sandcastle_worker.py", line 1266, in g