Add missing __getitem__
and other attributes to BitLocations
(backport #13997)
#14008
+75
−1
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.
Fixes #13996
Summary
We accidentaly removed the capability of indexing a
BitLocation
object. These commits add that functionality back!Details and comments
In an oversight after #13860, when switching to use the pyo3 friendly
BitLocations
which is not an instance ofnamedtuple
we did not extend it to include sequence methods__getitem__
and__len__
, which results in breaking api changes.The following commits add those methods to
BitLocations
and also labels the class correctly as asequence
in PyO3.This is an automatic backport of pull request #13997 done by [Mergify](https://mergify.com).