Raise a TypeError when slice-setting a Multirange with a non-iterable value #129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The type declaration is:
so passing a non-iterable value should not be allowed. However, the
method implementation makes a special-case for non-iterable values with
a slice.
In accordance with MutableSequence behavior, e.g.:
it seems more correct to raise a TypeError.
(Alternatively, we could change the type declaration of
MultiRange__setitem__()but that would make it incompatible withMutableSequence, which seems wrong.)