Closed srittau closed 8 months ago
It did not supported arbitrary iterables initially, it only worked with sequences. Then in 3.6 it started working with non-empty iterables by accident, but it was not intentional change, it was an implementation detail.
Accepting an arbitrary iterable is a new feature. This change can only go in future 3.13.
Please revert the change in versionchanged:: 3.6
and add versionchanged:: 3.13
.
Thanks, done in https://github.com/python/cpython/pull/115639
Bug report
Bug description:
This came up in python/typeshed#11310: When passing an empty sequence to
commonpath()
, aValueError
is raised with an appropriate error message. When an "empty" iterable is passed, anIndexError
is raised instead, although iterables otherwise work fine:The fix is trivial, I'll send a PR. Technically this is an API change, though, although the old API is unexpected.
CPython versions tested on:
3.11, 3.12
Operating systems tested on:
Linux
Linked PRs