issues

Table actions

3 rows where repo = 13221727, type = "pull" and user = 1486942 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

  • pull · 3 ✖

state 1

repo 1

  • xarray · 3 ✖
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
1952720792 PR_kwDOAMm_X85dTIJ7 8338 Enable subclassing the netCDF4 backend, changing the dataset class ZedThree 1486942 closed 0     4 2023-10-19T17:09:22Z 2023-12-04T17:16:50Z 2023-12-04T17:16:49Z CONTRIBUTOR   0 pydata/xarray/pulls/8338

See #8288

  • [ ] Closes #xxxx
  • [ ] Tests added
  • [ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
  • [ ] New functions/methods are listed in api.rst

These changes allow me to make a pretty minimal subclass that just swaps out the netCDF4.Dataset class for my version:

```python from xarray.backends.netCDF4_ import NetCDF4BackendEntrypoint, NetCDF4DataStore from ._wrapper import Dataset # This is my netCDF extension

class NcComplexDataStore(NetCDF4DataStore): @classmethod def DatasetClass(self) -> type: return Dataset

class NcComplexBackendEntrypoint(NetCDF4BackendEntrypoint): DataStore = NcComplexDataStore ```

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8338/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1949710368 PR_kwDOAMm_X85dI74W 8331 Docs: Add syntax for registering backends in `pyproject.toml` ZedThree 1486942 closed 0     3 2023-10-18T13:06:55Z 2023-10-19T12:47:45Z 2023-10-19T12:47:34Z CONTRIBUTOR   0 pydata/xarray/pulls/8331

Uses sphinx-inline-tabs for pretty and compact options.

Also reword surrounding text a little for clarity.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8331/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
1807517529 PR_kwDOAMm_X85VqE9h 7995 Use variable name in all exceptions raised in `as_variable` ZedThree 1486942 closed 0     5 2023-07-17T11:03:32Z 2023-07-17T15:33:50Z 2023-07-17T14:59:39Z CONTRIBUTOR   0 pydata/xarray/pulls/7995

This is more consistent with the other exceptions raised in this function, and helps to more quickly diagnose issues when e.g. creating datasets.

  • [x] User visible changes (including notable bug fixes) are documented in whats-new.rst

Is this a large enough change to warrant an entry in whats-new?

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