issues

Table actions

2 rows where user = 1256994 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

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
443958810 MDExOlB1bGxSZXF1ZXN0Mjc4NzE4MTI0 2960 fix Docstring of xr.Dataset.info() to avoid failures when updating to numpydoc>=0.9 MaxBo 1256994 closed 0     1 2019-05-14T14:46:58Z 2019-09-23T16:50:37Z 2019-05-14T15:37:23Z CONTRIBUTOR   0 pydata/xarray/pulls/2960

fix Docstring of xr.Dataset.info() to avoid failures when updating to numpydoc>=0.9 - [ X ] Closes #2959 - [ ] Tests added - [ ] Fully documented, including whats-new.rst for all changes and api.rst for new API

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2960/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
443958276 MDU6SXNzdWU0NDM5NTgyNzY= 2959 Docstring for Dataset.info fails with numpydoc 0.9 MaxBo 1256994 closed 0     0 2019-05-14T14:46:01Z 2019-05-14T15:37:23Z 2019-05-14T15:37:23Z CONTRIBUTOR      

The docstring for xr.Dataset.info breaks the sphinx-documentation when using numpydoc 0.9. I noticed this when i tried to build sphnix documentation of a class that subclassed xr.Dataset.

I wrote a pull-request to fix this issue when xarray should update from numpydoc 0.8 to to numpydoc 0.9 one day. 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2959/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]);