home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

where issue = 245468219 and user = 1217238 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
318119534 https://github.com/pydata/xarray/issues/1487#issuecomment-318119534 https://api.github.com/repos/pydata/xarray/issues/1487 MDEyOklzc3VlQ29tbWVudDMxODExOTUzNA== shoyer 1217238 2017-07-26T17:08:12Z 2017-07-26T17:08:12Z MEMBER

I was under the impression that xarray.DataArrays behave the same as numpy.ndarrays when applying numpy functions, so that I didn't have to change any of my code.

We do attempt to make this work when feasible, but unfortunately it isn't always the case. In this case I do think this is doable, so I'm marking this issue as "Contributions welcome."

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  `axis` keyword ignored when applying `np.squeeze` to `DataArray` 245468219
317871442 https://github.com/pydata/xarray/issues/1487#issuecomment-317871442 https://api.github.com/repos/pydata/xarray/issues/1487 MDEyOklzc3VlQ29tbWVudDMxNzg3MTQ0Mg== shoyer 1217238 2017-07-25T21:02:59Z 2017-07-25T21:02:59Z MEMBER

This is (somewhat) expected. Basically, you should use the DataArray.squeeze() method instead.

The long story is that some but not all NumPy functions define themselves by (attempting) to call methods, e.g., np.squeeze(array) -> array.squeeze().

squeeze is a special and somewhat surprising case. Apparently np.squeeze(array, axis) -> array.squeeze(axis) -> array.squeeze() if the axis argument isn't handled. But we didn't bother to define an axis argument for DataArray.squeeze(), so this results in an error.

I suppose we could fix this by defining an axis argument, like we do for some methods like .mean(). But the short answer is that using xarray methods should be preferred.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  `axis` keyword ignored when applying `np.squeeze` to `DataArray` 245468219

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]);
Powered by Datasette · Queries took 4646.957ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows