home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

7 rows where author_association = "MEMBER", issue = 124867009 and user = 1217238 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

  • shoyer · 7 ✖

issue 1

  • Complete renaming xray -> xarray · 7 ✖

author_association 1

  • MEMBER · 7 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
171760492 https://github.com/pydata/xarray/issues/704#issuecomment-171760492 https://api.github.com/repos/pydata/xarray/issues/704 MDEyOklzc3VlQ29tbWVudDE3MTc2MDQ5Mg== shoyer 1217238 2016-01-14T19:52:27Z 2016-01-14T19:52:27Z MEMBER

Looks like import xarray as xr it is!

My plan here is to follow IPython's example and simultaneously release version 0.7 of xray and xarray. The former will include a deprecation warning when you import xray advising you to update your code.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Complete renaming xray -> xarray 124867009
169475864 https://github.com/pydata/xarray/issues/704#issuecomment-169475864 https://api.github.com/repos/pydata/xarray/issues/704 MDEyOklzc3VlQ29tbWVudDE2OTQ3NTg2NA== shoyer 1217238 2016-01-06T21:59:16Z 2016-01-07T02:33:41Z MEMBER

Ah, I see. People have commented on that before.

edit: fixed and tweaked

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Complete renaming xray -> xarray 124867009
169466960 https://github.com/pydata/xarray/issues/704#issuecomment-169466960 https://api.github.com/repos/pydata/xarray/issues/704 MDEyOklzc3VlQ29tbWVudDE2OTQ2Njk2MA== shoyer 1217238 2016-01-06T21:23:58Z 2016-01-06T21:35:07Z MEMBER

I think that's beyond the limits of my graphical design talent :). I actually whipped up the logo in LaTeX!

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Complete renaming xray -> xarray 124867009
169423162 https://github.com/pydata/xarray/issues/704#issuecomment-169423162 https://api.github.com/repos/pydata/xarray/issues/704 MDEyOklzc3VlQ29tbWVudDE2OTQyMzE2Mg== shoyer 1217238 2016-01-06T19:08:32Z 2016-01-06T19:08:32Z MEMBER

Making some progress on this...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Complete renaming xray -> xarray 124867009
168862078 https://github.com/pydata/xarray/issues/704#issuecomment-168862078 https://api.github.com/repos/pydata/xarray/issues/704 MDEyOklzc3VlQ29tbWVudDE2ODg2MjA3OA== shoyer 1217238 2016-01-05T01:17:47Z 2016-01-05T01:17:47Z MEMBER

The name xarray is not final until we make a release :). But we've been tossing around names for a while (e.g., see this Twitter discussion)and I do think it's probably the best choice, given that we are starting from xray rather than a blank slate.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Complete renaming xray -> xarray 124867009
168854213 https://github.com/pydata/xarray/issues/704#issuecomment-168854213 https://api.github.com/repos/pydata/xarray/issues/704 MDEyOklzc3VlQ29tbWVudDE2ODg1NDIxMw== shoyer 1217238 2016-01-05T00:34:31Z 2016-01-05T00:34:31Z MEMBER

I know renaming causes pain. But it is a pretty serious name conflict with xray science, and in the long terms, I think the future is bright enough that it's worth the short term pain. The name xarray will hopefully minimize confusion.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Complete renaming xray -> xarray 124867009
168852670 https://github.com/pydata/xarray/issues/704#issuecomment-168852670 https://api.github.com/repos/pydata/xarray/issues/704 MDEyOklzc3VlQ29tbWVudDE2ODg1MjY3MA== shoyer 1217238 2016-01-05T00:24:02Z 2016-01-05T00:25:01Z MEMBER

As part of this rename, we need to decide the recommended way to import xarray.

Some options for abbreviations: xr, xa, xry. Any thoughts?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Complete renaming xray -> xarray 124867009

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 208.883ms · About: xarray-datasette