issue_comments

Table actions

3 rows where issue = 103703011 and user = 1217238 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

  • shoyer · 3 ✖

issue 1

  • operation on complex number data · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
394439118 https://github.com/pydata/xarray/issues/553#issuecomment-394439118 https://api.github.com/repos/pydata/xarray/issues/553 MDEyOklzc3VlQ29tbWVudDM5NDQzOTExOA== shoyer 1217238 2018-06-04T17:43:12Z 2018-06-04T17:43:12Z MEMBER

The short answer is that we shouldn't remove xarray.ufuncs.angle until NumPy has a satisfactory overload mechanism for it. This might mean something like http://www.numpy.org/neps/nep-0018-array-function-protocol.html instead.

PendingDeprecationWarning is the weakest form of deprecation warning. Basically it means "We plan to deprecate it in the future, but haven't done so yet."

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   operation on complex number data 103703011
334799615 https://github.com/pydata/xarray/issues/553#issuecomment-334799615 https://api.github.com/repos/pydata/xarray/issues/553 MDEyOklzc3VlQ29tbWVudDMzNDc5OTYxNQ== shoyer 1217238 2017-10-06T16:08:31Z 2017-10-06T16:08:31Z MEMBER

You can also use xarray.ufuncs.angle() for this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   operation on complex number data 103703011
135988109 https://github.com/pydata/xarray/issues/553#issuecomment-135988109 https://api.github.com/repos/pydata/xarray/issues/553 MDEyOklzc3VlQ29tbWVudDEzNTk4ODEwOQ== shoyer 1217238 2015-08-29T13:44:28Z 2015-08-29T13:44:28Z MEMBER

There's nothing we can do about np.angle, np.real and np.imag unfortunately -- these need to be updated on the numpy side to call __array_wrap__.

However, we could certainly add .real and .imag properties that access these computed values as DataArrays.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   operation on complex number data 103703011

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