pull_requests: 1726642719
This data as json
id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1726642719 | PR_kwDOAMm_X85m6nof | 8750 | closed | 0 | refactor `indexing.py`: introduce `.oindex` for Explicitly Indexed Arrays | 13301940 | <!-- Feel free to remove check-list items aren't relevant to your change --> this pull request represents an initial effort to refactor the indexing logic within `indexing.py` by separating it from `variable.py`. to enhance the flexibility of explicitly indexed array classes, this PR introduces orthogonal ~~and vectorized~~ indexing methods—`.oindex[key]` ~~and `.vindex[key[`~~. these changes are a part of a broader initiative aimed at enabling indexing support for namedarray - [x] Towards https://github.com/pydata/xarray/issues/8238 - [ ] Tests added - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] New functions/methods are listed in `api.rst` edit 1: - to minimize the blast radius of this PR, i decided to just focus on `oindex[key]` method in this PR. i intend to introduce `vindex[key]` in a separate PR ## TODO: - [x] https://github.com/pydata/xarray/pull/8750#discussion_r1491169460 - [ ] Enable passing the underlying tuple key | 2024-02-14T23:53:53Z | 2024-02-23T23:34:44Z | 2024-02-23T23:34:43Z | 2024-02-23T23:34:43Z | d9760f30662b219182cdc8dedc04dfbe7771942b | 0 | c38c9003fb616da10014ee7e4a99d5be366cad48 | 01f7b4ff54c9e6b41c9a7b45e6dd0039992075ee | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/8750 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests