issues

Table actions

2 rows where state = "closed" and user = 14014177 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 2

state 1

  • closed · 2 ✖

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
197057007 MDExOlB1bGxSZXF1ZXN0OTkwMjIzODE= 1178 Fix inconsistent behaviour for xarray.DataArray.rename magonser 14014177 closed 0     4 2016-12-21T23:18:24Z 2016-12-23T17:26:41Z 2016-12-23T17:26:32Z CONTRIBUTOR   0 pydata/xarray/pulls/1178

Attempt to fix #1177

Please let me know, if PR requires further refinement. 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1178/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
196984274 MDU6SXNzdWUxOTY5ODQyNzQ= 1177 Inconsistent behaviour for xarray.DataArray.rename magonser 14014177 closed 0     1 2016-12-21T17:05:47Z 2016-12-23T17:26:32Z 2016-12-23T17:26:32Z CONTRIBUTOR      

Hi,

thanks for creating xarray, I like it a lot. However I want to ask, why the behaviour of xarray.DataArray.rename is so incosistent:

python import xarray as xr x = xr.DataArray([1, 2, 3], dims=('a',), coords={'a': [1, 2, 3]}, name='a') x.rename({'a': 'b'})

renames the name of x not the coordinate! Could you explain the behaviour to me? I do not understand it, or consider it as inconsistent.

Thanks, Markus

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/1177/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed xarray 13221727 issue

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);