issue_comments

Table actions

1 row where issue = 840258082 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • keewis · 1 ✖

issue 1

  • `lock` kwarg needs a deprecation cycle? · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
807145690 https://github.com/pydata/xarray/issues/5073#issuecomment-807145690 https://api.github.com/repos/pydata/xarray/issues/5073 MDEyOklzc3VlQ29tbWVudDgwNzE0NTY5MA== keewis 14808389 2021-03-25T17:29:57Z 2021-03-25T17:30:57Z MEMBER

as far as I understand the docs of DeprecationWarning and FutureWarning, the main difference is the intended target audience in a traditional library vs. application setting (where libraries are always used to write applications): PendingDeprecationWarning and DeprecationWarning are used to signal deprecations in the library, while FutureWarning are intended for users of the application. Interestingly, PEP565 mentions that FutureWarning can also be used for changed semantics of valid code.

If we follow that, xarray should not issue FutureWarning (other than to report changing semantics) because it is a library and both interactive and scripted use would be similar to writing a application.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `lock` kwarg needs a deprecation cycle? 840258082

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