home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 1246569430

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/pull/6971#issuecomment-1246569430 https://api.github.com/repos/pydata/xarray/issues/6971 1246569430 IC_kwDOAMm_X85KTSPW 4160723 2022-09-14T10:33:17Z 2022-09-14T10:33:17Z MEMBER

Have you thought about whether we might want to expose a separate public xarray.indexes namespace?

Yes I've been thinking about it and I agree I find it cleaner than exposing all of this in Xarray's main namespace. There's a few (minor) cons, though:

  • I think the indexes.py and indexing.py modules and their content are well located in core
  • We could create a xarray/indexes/__init__.py and import there a few "public" classes from core, but is it worth it? I'm not sure if the number of Xarray built-in indexes will grow much beyond PandasIndex and PandasMultiIndex. Perhaps it's preferable not?
  • Things like CFTimeIndex are already imported in Xarray's main namespace
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  1357296406
Powered by Datasette · Queries took 0.58ms · About: xarray-datasette