issue_comments

Table actions

3 rows where issue = 288466108 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

  • Drop support for Python 2 · 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
361824307 https://github.com/pydata/xarray/issues/1830#issuecomment-361824307 https://api.github.com/repos/pydata/xarray/issues/1830 MDEyOklzc3VlQ29tbWVudDM2MTgyNDMwNw== shoyer 1217238 2018-01-31T04:59:55Z 2018-01-31T04:59:55Z MEMBER

I don't object to the timeline, but I don't think we're ready to commit to supporting Python 2 for all 0.X releases and stopping it with 1.0. The particular version number feels premature to me.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Drop support for Python 2 288466108
361808641 https://github.com/pydata/xarray/issues/1830#issuecomment-361808641 https://api.github.com/repos/pydata/xarray/issues/1830 MDEyOklzc3VlQ29tbWVudDM2MTgwODY0MQ== shoyer 1217238 2018-01-31T03:00:47Z 2018-01-31T03:00:47Z MEMBER

My inclination would be to save 1.0 until xarray's data model is stable, which probably means after https://github.com/pydata/xarray/issues/1603. If the timing works out for dropping Python 2 support that would be great, but I wouldn't want to force it.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Drop support for Python 2 288466108
357770710 https://github.com/pydata/xarray/issues/1830#issuecomment-357770710 https://api.github.com/repos/pydata/xarray/issues/1830 MDEyOklzc3VlQ29tbWVudDM1Nzc3MDcxMA== shoyer 1217238 2018-01-15T19:33:09Z 2018-01-15T19:33:09Z MEMBER

My inclination would be to follow the lead of pandas here, since it's unlikely to make sense to update xarray without its dependencies. So I guess end of 2018 makes sense?

 
{
    "total_count": 4,
    "+1": 4,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Drop support for Python 2 288466108

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