issue_comments

Table actions

4 rows where issue = 671019427 and user = 221526 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

  • dopplershift · 4 ✖

issue 1

  • We shouldn't require a recent version of setuptools to install xarray · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
668891516 https://github.com/pydata/xarray/issues/4295#issuecomment-668891516 https://api.github.com/repos/pydata/xarray/issues/4295 MDEyOklzc3VlQ29tbWVudDY2ODg5MTUxNg== dopplershift 221526 2020-08-05T00:07:38Z 2020-08-05T00:07:38Z CONTRIBUTOR

cough Solving the "setuptools won't work in setup_requires because it's too late" was basically the entire driving force of pyproject.toml.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   We shouldn't require a recent version of setuptools to install xarray 671019427
668405710 https://github.com/pydata/xarray/issues/4295#issuecomment-668405710 https://api.github.com/repos/pydata/xarray/issues/4295 MDEyOklzc3VlQ29tbWVudDY2ODQwNTcxMA== dopplershift 221526 2020-08-04T06:27:20Z 2020-08-04T06:27:20Z CONTRIBUTOR

Wow...two years for pip to gain support...I would not have expected that.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   We shouldn't require a recent version of setuptools to install xarray 671019427
668395780 https://github.com/pydata/xarray/issues/4295#issuecomment-668395780 https://api.github.com/repos/pydata/xarray/issues/4295 MDEyOklzc3VlQ29tbWVudDY2ODM5NTc4MA== dopplershift 221526 2020-08-04T05:56:44Z 2020-08-04T05:56:44Z CONTRIBUTOR

I'm not here to argue, but pyproject.toml was introduced in PEP-518, which was accepted over 4 years ago. I know packaging moves slowly but I'm curious how long something has to be around before becoming "established" and ceases to be "novel". 😉

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   We shouldn't require a recent version of setuptools to install xarray 671019427
667581142 https://github.com/pydata/xarray/issues/4295#issuecomment-667581142 https://api.github.com/repos/pydata/xarray/issues/4295 MDEyOklzc3VlQ29tbWVudDY2NzU4MTE0Mg== dopplershift 221526 2020-08-01T20:10:55Z 2020-08-01T20:10:55Z CONTRIBUTOR

Rolling window seems fine to me. I will say that I don't generally bother bumping that on other projects until we run into an issue/new feature that necessitates it, though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   We shouldn't require a recent version of setuptools to install xarray 671019427

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