You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable explicit use of key tuples (instead of *Indexer objects) in indexing adapters and explicitly indexed arrays (#8870)
* pass key tuple to indexing adapters and explicitly indexed arrays
* update indexing in StackedBytesArray
* Update indexing in StackedBytesArray
* Add _IndexerKey type to _typing.py
* Update indexing in StackedBytesArray
* use tuple indexing in test_backend_array_deprecation_warning
* Add support for CompatIndexedTuple in explicit indexing adapter
This commit updates the `explicit_indexing_adapter` function to accept both
`ExplicitIndexer` and the new `CompatIndexedTuple`. The `CompatIndexedTuple` is
designed to facilitate the transition towards using raw tuples by carrying
additional metadata about the indexing type (basic, vectorized, or outer).
* remove unused code
* type hint fixes
* fix docstrings
* fix tests
* fix docstrings
* Apply suggestions from code review
Co-authored-by: Deepak Cherian <dcherian@users.noreply.github.com>
* update docstrings and pass tuples directly
* Some test cleanup
* update docstring
* use `BasicIndexer` instead of `CompatIndexedTuple`
* support explicit indexing with tuples
* fix mypy errors
* remove unused IndexerMaker
* Update LazilyIndexedArray._updated_key to support explicit indexing with tuples
---------
Co-authored-by: Deepak Cherian <dcherian@users.noreply.github.com>
Co-authored-by: Deepak Cherian <deepak@cherian.net>
0 commit comments