issue_comments

Table actions

1 row where issue = 602256880 and user = 2448579 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

  • dcherian · 1 ✖

issue 1

  • [Proposal] Expose Variable without Pandas dependency · 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
665746983 https://github.com/pydata/xarray/issues/3981#issuecomment-665746983 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDY2NTc0Njk4Mw== dcherian 2448579 2020-07-29T15:52:17Z 2020-07-29T15:57:00Z MEMBER

Another possible outcome is that pandas becomes optional as part of the indexing refactor, and we expose Variable as public API.

BUT @shoyer has been consistent against making Variable public, so maybe the best option is to fork it out to xarray-contrib/variable?

EDIT: The git log for variable.py shows really minor changes over the past year or two (https://github.com/pydata/xarray/commits/master/xarray/core/variable.py) — mostly adding new method (e.g. pad & quantile) and some NEP-18 work. So it seems pretty stable and perhaps not much effort to exchange future patches between xarray and the fork.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Proposal] Expose Variable without Pandas dependency 602256880

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