issue_comments

Table actions

3 rows where issue = 1052740367 and user = 10194086 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • mathause · 3 ✖

issue 1

  • preserve chunked data when creating DataArray from DataArray · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
983747745 https://github.com/pydata/xarray/pull/5984#issuecomment-983747745 https://api.github.com/repos/pydata/xarray/issues/5984 IC_kwDOAMm_X846osyh mathause 10194086 2021-12-01T15:22:27Z 2021-12-01T15:22:27Z MEMBER

Any objections to merging this as is? If we don't disallow xr.DataArray(da) this is a clear advantage over the current version.

However,

```python xr.DataArray(da).data is da.data # True xr.DataArray(da.data).data is da.data # True

while

da.copy().data is da.data # False (deep=True is the default) ``` might just be surprising in some situations.

(Just for completeness - xr.DataArray(da, **kwargs) does a good job at erroring if the kwargs are not compatible with da.)

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   preserve chunked data when creating DataArray from DataArray 1052740367
979096277 https://github.com/pydata/xarray/pull/5984#issuecomment-979096277 https://api.github.com/repos/pydata/xarray/issues/5984 IC_kwDOAMm_X846W9LV mathause 10194086 2021-11-25T11:02:18Z 2021-11-25T11:02:18Z MEMBER

How about we raise DeprecationWarning for now asking the user to pass in .data instead.

Makes sense - how about:

python msg = ( "Passing a `DataArray` object to the `DataArray` constructor is ambiguous.\n" "Pass `da.data`, or use `da.copy(deep=True)`, or one of the `xarray.*_like` (e.g. " "`xarray.zeros_like`) functions instead,\n" "depending on your use case." ) warnings.warn(msg, FutureWarning)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   preserve chunked data when creating DataArray from DataArray 1052740367
977689446 https://github.com/pydata/xarray/pull/5984#issuecomment-977689446 https://api.github.com/repos/pydata/xarray/issues/5984 IC_kwDOAMm_X846Rltm mathause 10194086 2021-11-24T09:23:14Z 2021-11-24T09:23:14Z MEMBER

@dcherian you had an opinion on this in #5983 - would you rather raise a ValueError here and advise to pass da.data? 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   preserve chunked data when creating DataArray from DataArray 1052740367

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]);