issue_comments

Table actions

5 rows where author_association = "MEMBER", issue = 626083981 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

These facets timed out: author_association, issue

user 1

  • shoyer · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
803443559 https://github.com/pydata/xarray/pull/4102#issuecomment-803443559 https://api.github.com/repos/pydata/xarray/issues/4102 MDEyOklzc3VlQ29tbWVudDgwMzQ0MzU1OQ== shoyer 1217238 2021-03-20T18:45:59Z 2021-03-20T18:45:59Z MEMBER

I suspect we could make Pooch work OK by tagging releases in the xarray-data repository. Then we can manually update the version number inside xarray whenever we add or update a dataset.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cache rasterio example files 626083981
803440144 https://github.com/pydata/xarray/pull/4102#issuecomment-803440144 https://api.github.com/repos/pydata/xarray/issues/4102 MDEyOklzc3VlQ29tbWVudDgwMzQ0MDE0NA== shoyer 1217238 2021-03-20T18:29:55Z 2021-03-20T18:29:55Z MEMBER

I don't think it's important to preserve the GitHub URL and branch options. I suspect those options exist strictly for testing new datasets.

I'm surprised that Pooch seems to be focused on data that is bundled in code repositories. It seems like that could easily lead to bloated repositories (though I guess xarray data is bigger than image data, for example).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cache rasterio example files 626083981
651510424 https://github.com/pydata/xarray/pull/4102#issuecomment-651510424 https://api.github.com/repos/pydata/xarray/issues/4102 MDEyOklzc3VlQ29tbWVudDY1MTUxMDQyNA== shoyer 1217238 2020-06-30T03:43:47Z 2020-06-30T03:43:47Z MEMBER

I vendored appdirs.user_cache_dir, but I need help with mypy: the windows code uses ctypes.windll which is only available on windows

Let's skip this module for mypy. You can add it to the list in setup.cfg. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cache rasterio example files 626083981
651224155 https://github.com/pydata/xarray/pull/4102#issuecomment-651224155 https://api.github.com/repos/pydata/xarray/issues/4102 MDEyOklzc3VlQ29tbWVudDY1MTIyNDE1NQ== shoyer 1217238 2020-06-29T16:21:29Z 2020-06-29T16:21:29Z MEMBER

Edit: appdirs solves that (but: it's a new dependency)

See #2815 :)

As mentioned in that issue, we could definitely vendor a copy of appdirs if desired. Or we could pick some simple heuristic. In practice I think ~/.cache is fine. It's only standard on Linux, but I have a handful of directories there on my Mac laptop already.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cache rasterio example files 626083981
650942527 https://github.com/pydata/xarray/pull/4102#issuecomment-650942527 https://api.github.com/repos/pydata/xarray/issues/4102 MDEyOklzc3VlQ29tbWVudDY1MDk0MjUyNw== shoyer 1217238 2020-06-29T06:11:18Z 2020-06-29T06:11:18Z MEMBER

Edit: I also changed the default cache directory to ~/.cache/xarray_tutorial_data with a fallback to the old default if ~/.cache does not exist

I would suggest just creating the full directory tree, e.g., with os.makedirs(path, exist_ok=True). I don't think we want to let this be inconsistent.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   cache rasterio example files 626083981

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