home / github / issues

Menu
  • GraphQL API
  • Search all tables

issues: 2135390562

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
2135390562 PR_kwDOAMm_X85m6nof 8750 refactor `indexing.py`: introduce `.oindex` for Explicitly Indexed Arrays 13301940 closed 0     2 2024-02-14T23:53:53Z 2024-02-23T23:34:44Z 2024-02-23T23:34:43Z MEMBER   0 pydata/xarray/pulls/8750

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
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8750/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    13221727 pull

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 0 rows from issue in issue_comments
Powered by Datasette · Queries took 0.5ms · About: xarray-datasette