[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Change by Alex Waygood : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

miss-islington added the comment: New changeset 9a9061d1ca7e28dc2b7e326153e933872c7cd452 by Miss Islington (bot) in branch '3.9': bpo-20369: concurrent.futures.wait() now deduplicates futures given a… (GH-30168) https://github.com/python/cpython/commit/9a9061d1ca7e28dc2b7e326153e933872c7cd452

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

miss-islington added the comment: New changeset ba124672d7bf490bea2930a3e8371823db5d4cae by Miss Islington (bot) in branch '3.10': bpo-20369: concurrent.futures.wait() now deduplicates futures given a… (GH-30168) https://github.com/python/cpython/commit/ba124672d7bf490bea2930a3e8371823db5d4ca

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Change by miss-islington : -- pull_requests: +28609 pull_request: https://github.com/python/cpython/pull/30401 ___ Python tracker ___ __

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Pablo Galindo Salgado added the comment: New changeset 7d7817cf0f826e566d8370a0e974bbfed6611d91 by Kumar Aditya in branch 'main': bpo-20369: concurrent.futures.wait() now deduplicates futures given a… (GH-30168) https://github.com/python/cpython/commit/7d7817cf0f826e566d8370a0e974bbfed6611d91

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +28608 pull_request: https://github.com/python/cpython/pull/30400 ___ Python tracker _

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Change by Mark Dickinson : -- nosy: -mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Change by Kumar Aditya : -- keywords: +patch nosy: +kumaraditya303 nosy_count: 4.0 -> 5.0 pull_requests: +28385 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30168 ___ Python tracker

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Change by Irit Katriel : -- keywords: +easy -patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Irit Katriel added the comment: Reproduced on 3.11. -- components: +Library (Lib) nosy: +iritkatriel type: -> behavior versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.3, Python 3.4 ___ Python tracker

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Changes by Glenn Langford : -- nosy: -glangford ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Glenn Langford added the comment: Updated patch with change to Doc/library/concurrent.futures.rst. -- Added file: http://bugs.python.org/file33751/issue20369.patch ___ Python tracker ___

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Glenn Langford added the comment: Updated patch with a test case, and added a minor note to the docstring to clarify behaviour. The use of sleep() in the test is not great, but it is the most obvious way to test and it is consistent with the approach used in other concurrent test cases. -

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

Glenn Langford added the comment: Proposed patch...please treat with an appropriate level of suspicion since this is my first patch submission. :-) A corresponding change will be made to as_completed() for #20367. Suggestions welcome. -- keywords: +patch Added file: http://bugs.pyth

[issue20369] concurrent.futures.wait() blocks forever when given duplicate Futures

New submission from Glenn Langford: For a Future f which has already completed, wait( [f,f], return_when=ALL_COMPLETED ) blocks forever. This is because the test in wait(): if len(done) == len(fs) is comparing the length of a set to the length of a list. If f has not completed, wait( [