bpo-41938: fixed wait calling len on iterables#22555
bpo-41938: fixed wait calling len on iterables#22555rohitkg98 wants to merge 1 commit intopython:mainfrom
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
MaxwellDupre
left a comment
MaxwellDupre
left a comment
There was a problem hiding this comment.
Looks like this is already in 3.11.0.a4.
But I don't see any test associated with the change.
|
Thanks for this contribution, however, it looks like it was already fixed in #30168 |
6 participants
concurrent.futures.wait was calling
len()on possible iterables and we were converting the argument to set anyways. so just changed it to set from start.checkout this issue41938 for more details.
https://bugs.python.org/issue41938