issue_comments

Table actions

5 rows where issue = 628436420 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 2

issue 1

  • xarray ufuncs · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1101039166 https://github.com/pydata/xarray/issues/4116#issuecomment-1101039166 https://api.github.com/repos/pydata/xarray/issues/4116 IC_kwDOAMm_X85BoIY- stale[bot] 26384082 2022-04-18T02:43:46Z 2022-04-18T02:43:46Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray ufuncs 628436420
648874567 https://github.com/pydata/xarray/issues/4116#issuecomment-648874567 https://api.github.com/repos/pydata/xarray/issues/4116 MDEyOklzc3VlQ29tbWVudDY0ODg3NDU2Nw== dcherian 2448579 2020-06-24T14:59:35Z 2020-06-24T14:59:35Z MEMBER

I think we should put that warning (removed after support for 1.17 is dropped) into the documentation, too.

:+1:

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray ufuncs 628436420
636887006 https://github.com/pydata/xarray/issues/4116#issuecomment-636887006 https://api.github.com/repos/pydata/xarray/issues/4116 MDEyOklzc3VlQ29tbWVudDYzNjg4NzAwNg== keewis 14808389 2020-06-01T14:17:58Z 2020-06-01T15:13:48Z MEMBER

actually, it seems we might need to wait a bit longer, the deprecation warning says we would remove the __array_function__ ufuncs only after we stopped supporting numpy < 1.17 (see #2615 where the warning was extended). That means we still could remove only a part of the module, or we could wait until we could remove the whole module. I think we should put that warning (removed after support for 1.17 is dropped) into the documentation, too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray ufuncs 628436420
636864612 https://github.com/pydata/xarray/issues/4116#issuecomment-636864612 https://api.github.com/repos/pydata/xarray/issues/4116 MDEyOklzc3VlQ29tbWVudDYzNjg2NDYxMg== keewis 14808389 2020-06-01T13:35:19Z 2020-06-01T13:35:19Z MEMBER

which suggestion do you mean? Removing the whole module or just the __array_ufunc__ functions?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray ufuncs 628436420
636862823 https://github.com/pydata/xarray/issues/4116#issuecomment-636862823 https://api.github.com/repos/pydata/xarray/issues/4116 MDEyOklzc3VlQ29tbWVudDYzNjg2MjgyMw== dcherian 2448579 2020-06-01T13:31:56Z 2020-06-01T13:31:56Z MEMBER

Sounds good to me

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray ufuncs 628436420

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