issue_comments

Table actions

3 rows where issue = 876394165 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

author_association 3

issue 1

  • Export ufuncs from DataArray API · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
834415185 https://github.com/pydata/xarray/issues/5261#issuecomment-834415185 https://api.github.com/repos/pydata/xarray/issues/5261 MDEyOklzc3VlQ29tbWVudDgzNDQxNTE4NQ== seth-p 7441788 2021-05-07T13:51:46Z 2021-05-07T13:53:08Z CONTRIBUTOR

I'm wondering if one could just have a generic implementation of DataArray.func(*args, **kwargs) for any unrecognized "func" that calls np.func(self, *args, **kwargs) (perhaps conditional on some global numpy_fallthrough option)? And similarly for Dataset.func(*args, **kwargs).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Export ufuncs from DataArray API 876394165
832659229 https://github.com/pydata/xarray/issues/5261#issuecomment-832659229 https://api.github.com/repos/pydata/xarray/issues/5261 MDEyOklzc3VlQ29tbWVudDgzMjY1OTIyOQ== eric-czech 6130352 2021-05-05T12:47:43Z 2021-05-05T12:47:43Z NONE

In general, we are deprecating xr.ufuncs in favor of np.ufunc(DataArray)

Makes sense. It is a somewhat awkward distinction to teach though to those who wouldn't appreciate the __array_ufunc__ protocol compliance, especially since most other functionality we appeal to like reductions (e.g. max, min, sum), concat, merge, indexing, filtering, etc. comes through the Xarray APIs alone.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Export ufuncs from DataArray API 876394165
832652405 https://github.com/pydata/xarray/issues/5261#issuecomment-832652405 https://api.github.com/repos/pydata/xarray/issues/5261 MDEyOklzc3VlQ29tbWVudDgzMjY1MjQwNQ== dcherian 2448579 2021-05-05T12:37:07Z 2021-05-05T12:37:07Z MEMBER

I think adding isfinite would make sense, since we have isnull.

In general, we are deprecating xr.ufuncs in favor of np.ufunc(DataArray)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Export ufuncs from DataArray API 876394165

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