issues

Table actions

1 row where "closed_at" is on date 2020-08-05 and user = 226037 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
673061269 MDExOlB1bGxSZXF1ZXN0NDYyOTkwNzg1 4310 Remove all unused and warn-raising methods from AbstractDataStore alexamici 226037 closed 0     1 2020-08-04T20:27:57Z 2020-09-22T21:12:47Z 2020-08-05T14:27:51Z MEMBER   0 pydata/xarray/pulls/4310
  • [x] Related but really orthogonal to #4309
  • [x] Remove code, but keeps all existing tests passing (on MacOS with pandas=1.0.5)
  • [x] Passes isort . && black . && mypy . && flake8
  • [x] No user / developer visible changes are expected

@shoyer this could be the first pass of the simplification of the current backend API. It not needed for #4309, but it make more obvious that we'd be free to keep the AbstractDataStore class if we wanted to.

The reason the change can be considered reasonably innocuous is that warnings would have been printed on access to any of the removed methods, but you never know. Your call (but I'd love to have a delete-only contribution to xarray :D).

Please note that: 1. this change is the absolute lowest hanging fruit, 2. removing __enter__ and __exit__ appears feasible as they are used only in tests, but it is a slightly bigger change, 3. removing load is marginally more complex because it handle the special case when a variable name is equal to None.

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