home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where issue = 306067267 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 4

  • WeatherGod 1
  • shoyer 1
  • max-sixty 1
  • fmaussion 1

author_association 2

  • MEMBER 3
  • CONTRIBUTOR 1

issue 1

  • can't do in-place clip() with DataArrays. · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
588517800 https://github.com/pydata/xarray/issues/1997#issuecomment-588517800 https://api.github.com/repos/pydata/xarray/issues/1997 MDEyOklzc3VlQ29tbWVudDU4ODUxNzgwMA== max-sixty 5635139 2020-02-19T22:59:08Z 2020-02-19T22:59:08Z MEMBER

Closing as inplace generally removed, reopen if I'm missing something

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  can't do in-place clip() with DataArrays. 306067267
375909421 https://github.com/pydata/xarray/issues/1997#issuecomment-375909421 https://api.github.com/repos/pydata/xarray/issues/1997 MDEyOklzc3VlQ29tbWVudDM3NTkwOTQyMQ== fmaussion 10050469 2018-03-24T17:17:11Z 2018-03-24T17:17:11Z MEMBER

"we don't support out": Is that a general rule for xarray?

Not really, but the tendency is to go towards getting rid of inplace operations altogether. np.clip(foo, 0, 0.2, out=foo.values) will do what you want though.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  can't do in-place clip() with DataArrays. 306067267
373840044 https://github.com/pydata/xarray/issues/1997#issuecomment-373840044 https://api.github.com/repos/pydata/xarray/issues/1997 MDEyOklzc3VlQ29tbWVudDM3Mzg0MDA0NA== WeatherGod 291576 2018-03-16T20:45:39Z 2018-03-16T20:45:39Z CONTRIBUTOR

MaskedArrays had a similar problem, IIRC, because it was blindly copying the NDArray docstrings. Not going to be easy to do, though.

"we don't support out": Is that a general rule for xarray? Any notes on how to do what I want for clip? The function this was in was supposed to be general use (ndarrays and xarrays).

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  can't do in-place clip() with DataArrays. 306067267
373837176 https://github.com/pydata/xarray/issues/1997#issuecomment-373837176 https://api.github.com/repos/pydata/xarray/issues/1997 MDEyOklzc3VlQ29tbWVudDM3MzgzNzE3Ng== shoyer 1217238 2018-03-16T20:34:11Z 2018-03-16T20:34:11Z MEMBER

Hmm. We currently just blindly copy the docstring/method from NumPy here. We should probably update this to clarify that we don't support out.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  can't do in-place clip() with DataArrays. 306067267

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 14.1ms · About: xarray-datasette