home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where issue = 602256880 and user = 67612 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

  • matthew-brett · 3 ✖

issue 1

  • [Proposal] Expose Variable without Pandas dependency · 3 ✖

author_association 1

  • NONE 3
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
877607680 https://github.com/pydata/xarray/issues/3981#issuecomment-877607680 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDg3NzYwNzY4MA== matthew-brett 67612 2021-07-10T09:45:04Z 2021-07-10T09:45:04Z NONE

@shoyer - thanks for the feedback. I guess this means that it's unlikely this will be ready in time for our own CZI grant to finish (around June 2022)?

{
    "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
877403316 https://github.com/pydata/xarray/issues/3981#issuecomment-877403316 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDg3NzQwMzMxNg== matthew-brett 67612 2021-07-09T19:15:52Z 2021-07-09T19:15:52Z NONE

We were just talking about this over at https://github.com/nipy/nibabel - because we are about commit ourselves to an array-axis-labelling API. Is xarray-lite on the near or the distant horizon? Should we wait, to make our decisions? Mentioning @effigies because he reminded me about this thread.

{
    "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
665533405 https://github.com/pydata/xarray/issues/3981#issuecomment-665533405 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDY2NTUzMzQwNQ== matthew-brett 67612 2020-07-29T08:56:23Z 2020-07-29T08:56:23Z NONE

Just to add - we at Nibabel are very interested in adding labelled arrays with Xarray, but for us, the Pandas dependency is a serious problem. We're a base library for reading brain imaging formats, and we sit at the bottom of several imaging stacks, so it is very important to us that we don't introduce heavy dependencies - because we pass these on to all the libraries that depend on us. We've looked enviously at Xarray for a while, but the Pandas dependency is a serious-enough problem that we've held off from using it. Just for example, the Pandas dependency of Xarray was the reason that I was working on Datarray, to see if we could use that instead (we couldn't).

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