issues

Table actions

1 row where user = 5852283 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 1

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
456971151 MDExOlB1bGxSZXF1ZXN0Mjg4ODc1OTUz 3028 Add "errors" keyword argument to drop() and drop_dims() (#2994) andrew-c-ross 5852283 closed 0     5 2019-06-17T14:34:19Z 2019-06-20T15:48:00Z 2019-06-20T15:48:00Z CONTRIBUTOR   0 pydata/xarray/pulls/3028
  • [x] Closes #2994
  • [x] Tests added
  • [x] Fully documented, including whats-new.rst for all changes and api.rst for new API

This addresses #2994 by adding an "errors" keyword argument to Dataset.drop(), Dataset.drop_dims(), and DataArray.drop().

I stuck with pandas' convention of using either errors='raise', now the default that maintains previous behavior by raising an error if any passed label is not found in the dataset/array, or errors='ignore' in which case any missing labels are silently ignored.

This seems like a pretty straightforward change; mainly it is just skipping checks for missing labels when errors == 'ignore' and passing the errors keyword over to the pandas method when using index.drop(). Hopefully there are no subtleties that I've missed.

I added documentation to the appropriate methods, although I have been struggling to build the docs locally and am unsure if they look right.

Also this is my first attempt to contribute to any project, so suggestions and feedback are welcome. 

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

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