[issue41938] concurrent.futures.wait calls len() on an possible iterable
Change by Kaushal Rohit : -- keywords: +patch pull_requests: +21553 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22555 ___ Python tracker <https://bugs.python.org/issue41938> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41938] concurrent.futures.wait calls len() on an possible iterable
New submission from Kaushal Rohit : `fs` argument could be an iterable, and calling len on it would raise an Exception. We are converting `fs` into a set anyways for set difference, and that too twice. we can just put an `fs = set(fs)`. Let me know if we choose to go with that and I will make a PR ASAP. Thanks. -- components: Library (Lib) messages: 377991 nosy: rohitkg98 priority: normal severity: normal status: open title: concurrent.futures.wait calls len() on an possible iterable type: behavior versions: Python 3.10 ___ Python tracker <https://bugs.python.org/issue41938> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42001] Deprecate `typing.io` Wrapper Namespace
New submission from Kaushal Rohit : The `typing` module has a wrapper namespace in it called `typing.io` which contain I/O stream types. These types are now a part of the `typing` module itself. While we are at it, should we also deprecate `typing.re`? -- components: Library (Lib) messages: 378412 nosy: rohitkg98 priority: normal severity: normal status: open title: Deprecate `typing.io` Wrapper Namespace type: behavior versions: Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker <https://bugs.python.org/issue42001> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
