home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where author_association = "MEMBER", issue = 181033674 and user = 10050469 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

  • fmaussion · 4 ✖

issue 1

  • Attributes from netCDF4 intialization retained · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
289108562 https://github.com/pydata/xarray/pull/1038#issuecomment-289108562 https://api.github.com/repos/pydata/xarray/issues/1038 MDEyOklzc3VlQ29tbWVudDI4OTEwODU2Mg== fmaussion 10050469 2017-03-24T18:33:01Z 2017-03-24T18:33:01Z MEMBER

Yes, it also happened on this PR: https://github.com/pydata/xarray/pull/1328

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Attributes from netCDF4 intialization retained 181033674
288434764 https://github.com/pydata/xarray/pull/1038#issuecomment-288434764 https://api.github.com/repos/pydata/xarray/issues/1038 MDEyOklzc3VlQ29tbWVudDI4ODQzNDc2NA== fmaussion 10050469 2017-03-22T15:25:45Z 2017-03-22T15:25:45Z MEMBER

Note, I would say that open_mfdataset is no longer experimental because of its widespread use.

Yes, I also recently updated the IO docs in this respect and removed the experimental part: http://xarray.pydata.org/en/latest/io.html#id6

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Attributes from netCDF4 intialization retained 181033674
288425486 https://github.com/pydata/xarray/pull/1038#issuecomment-288425486 https://api.github.com/repos/pydata/xarray/issues/1038 MDEyOklzc3VlQ29tbWVudDI4ODQyNTQ4Ng== fmaussion 10050469 2017-03-22T14:57:54Z 2017-03-22T14:57:54Z MEMBER

Yes, that's good for me. I would mention it somewhere in the docstring though.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Attributes from netCDF4 intialization retained 181033674
267683615 https://github.com/pydata/xarray/pull/1038#issuecomment-267683615 https://api.github.com/repos/pydata/xarray/issues/1038 MDEyOklzc3VlQ29tbWVudDI2NzY4MzYxNQ== fmaussion 10050469 2016-12-16T20:03:10Z 2016-12-16T20:03:10Z MEMBER

AFAIC I'd be happy with a combined.attrs = datasets[0].attrs added before returning the combined dataset which is already better than the current situation...

Do you have time to get back to this @pwolfram ?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Attributes from netCDF4 intialization retained 181033674

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]);
Powered by Datasette · Queries took 2080.902ms · About: xarray-datasette