issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 1128304139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

issue 1

  • Indexing a RangeIndexed' DataArray with a RangeIndex returns a deprecated Int64Index · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1047241508 https://github.com/pydata/xarray/issues/6256#issuecomment-1047241508 https://api.github.com/repos/pydata/xarray/issues/6256 IC_kwDOAMm_X84-a6Mk benbovy 4160723 2022-02-21T21:28:56Z 2022-02-21T21:28:56Z MEMBER

This is still the same behavior with #5692.

We would need to handle pd.RangeIndex (and perhaps range?) label indexers similarly to slice label indexers, i.e., use pd.Index.slice_indexer internally to return integer indexers as slices (*).

```python b = my_da.sel(time=slice(0, 2)) b.get_index('time')

RangeIndex(start=0, stop=3, step=1, name='time')

```

Otherwise, label indexers get internally converted to arrays. Note that the conversion to an Int64Index is done in pandas (nothing specific is done on the Xarray side), so I expect that this will be eventually addressed in pandas. This conversion may not be too problematic if we consider this as an implementation detail (although I might be missing some important aspect).

```python idx = pd.RangeIndex(0, 100)

idx[slice(0, 3)]

RangeIndex(start=0, stop=3, step=1)

idx[[0, 1, 2]]

Int64Index([0, 1, 2], dtype='int64')

```

(*) One major difference is that in Xarray slice label indexers are upper-bound inclusive, while pd.RangeIndex and range are not!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Indexing a RangeIndexed' DataArray with a RangeIndex returns a deprecated Int64Index 1128304139
1046963193 https://github.com/pydata/xarray/issues/6256#issuecomment-1046963193 https://api.github.com/repos/pydata/xarray/issues/6256 IC_kwDOAMm_X84-Z2P5 mathause 10194086 2022-02-21T14:56:19Z 2022-02-21T15:01:13Z MEMBER

Thanks for the report - I guess RangeIndex was never very thoroughly tested. This may or may not change with #5692 (which is hopefully merged in the near future). So I suggest to wait for this.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Indexing a RangeIndexed' DataArray with a RangeIndex returns a deprecated Int64Index 1128304139

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);