issue_comments

Table actions

3 rows where issue = 602256880 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 · 3 ✖

issue 1

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

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
877464691 https://github.com/pydata/xarray/issues/3981#issuecomment-877464691 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDg3NzQ2NDY5MQ== shoyer 1217238 2021-07-09T21:25:25Z 2021-07-09T21:25:25Z MEMBER

We wrote a proposal to build an "xarray-lite" as part of a recent CZI application. We're still waiting to hear back, but if that's funded we'd definitely love to work with you on this.

On Fri, Jul 9, 2021 at 12:16 PM Matthew Brett @.***> wrote:

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 https://github.com/effigies because he reminded me about this thread.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/3981#issuecomment-877403316, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJJFVRJCOTD7TEROEW5RHDTW5DHHANCNFSM4MLCDJQQ . 

{
    "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
808677644 https://github.com/pydata/xarray/issues/3981#issuecomment-808677644 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDgwODY3NzY0NA== shoyer 1217238 2021-03-27T07:18:23Z 2021-03-27T07:18:23Z MEMBER

Thinking about this a little more, I would lean towards the separate package that xarray could depend upon. Perhaps we could all this xarr to denote a minimal version of xarray, unless that's too punny?

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   [Proposal] Expose Variable without Pandas dependency 602256880
665812548 https://github.com/pydata/xarray/issues/3981#issuecomment-665812548 https://api.github.com/repos/pydata/xarray/issues/3981 MDEyOklzc3VlQ29tbWVudDY2NTgxMjU0OA== shoyer 1217238 2020-07-29T17:58:50Z 2020-07-29T17:58:50Z MEMBER

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

Variable is a public API, which just don't encourage it for (most) users.

I think it would be relatively straightforward to expose xarray.Variable without the pandas dependency. We currently use pandas a little bit for input normalization in Variable and methods like isnull(), but we could likely add slower fallback option (or just not expose these features unless pandas is installed).

 
{
    "total_count": 2,
    "+1": 2,
    "-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]);