issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 168243768 and user = 5635139 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

  • max-sixty · 3 ✖

issue 1

  • Inconsistency between the types of Dataset.dims and DataArray.dims · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
236271882 https://github.com/pydata/xarray/issues/921#issuecomment-236271882 https://api.github.com/repos/pydata/xarray/issues/921 MDEyOklzc3VlQ29tbWVudDIzNjI3MTg4Mg== max-sixty 5635139 2016-07-29T19:26:50Z 2016-07-29T19:26:50Z MEMBER

Thanks for the, as ever, thoughtful response

Should we move Dataset.dims to be a tuple, then?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Inconsistency between the types of Dataset.dims and DataArray.dims 168243768
236224041 https://github.com/pydata/xarray/issues/921#issuecomment-236224041 https://api.github.com/repos/pydata/xarray/issues/921 MDEyOklzc3VlQ29tbWVudDIzNjIyNDA0MQ== max-sixty 5635139 2016-07-29T16:15:03Z 2016-07-29T16:15:03Z MEMBER

I frequently need to pull out the dimension names, and I've never needed to pull out their sizes. I realize that the internals need to do that though. And maybe my use case is specific.

Zooming out a bit: the access pattern for most of these (variables, coords) is indeed an OrderedDict of name to object. But the stickler for dim is why the size should be the value here? It seems very different from having dim objects as values.

I could certainly understand a convenience dims_shape (for {dim: ds[dim].shape for dim in ds.dims}.

But I"m coming from a place of less context without that much confidence...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Inconsistency between the types of Dataset.dims and DataArray.dims 168243768
236093456 https://github.com/pydata/xarray/issues/921#issuecomment-236093456 https://api.github.com/repos/pydata/xarray/issues/921 MDEyOklzc3VlQ29tbWVudDIzNjA5MzQ1Ng== max-sixty 5635139 2016-07-29T04:45:32Z 2016-07-29T04:45:32Z MEMBER

What are the arguments against having dims be a tuple for both DataArray & Datasets? 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Inconsistency between the types of Dataset.dims and DataArray.dims 168243768

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