issues

Table actions

2 rows where state = "open", type = "issue" and user = 4806877 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 1

  • issue · 2 ✖

state 1

  • open · 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
1319621859 I_kwDOAMm_X85Op9Tj 6837 Clarify difference between `.load()` and `.compute()` jsignell 4806877 open 0     8 2022-07-27T14:07:33Z 2022-07-27T22:30:22Z   CONTRIBUTOR      

What is your issue?

I just realized that the difference between .load() and .compute() is that .load() operates inplace and .compute() returns a new xarray object.I have 2 suggestions for how this could be clearer:

  1. Docs: the API docs for each method could reference the other.
  2. Code: this might be too big a change, but maybe .load() should not return anything. Consider this example from pandas: ```python import pandas as pd

df = pd.DataFrame({"air": []}) df.rename({"air": "foo"}, axis=1, inplace=True) # returns None since df is renamed inplace `` this matches the behavior of inplace actions in Python itself likelist.appendordict.update. This would be a major breaking change though, and it might be easier to just remove.load()` entirely.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/6837/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 issue
525970896 MDU6SXNzdWU1MjU5NzA4OTY= 3553 ENH: Plotting backend options jsignell 4806877 open 0     0 2019-11-20T17:54:45Z 2019-12-17T11:38:58Z   CONTRIBUTOR      

Since pandas has implemented entry_points based plotting backends, it seems reasonable that xarray would do the same. This would make it even easier to produce holoviews plots (rendered in bokeh via hvplot), by using the plot method rather than by importing hvplot directly.

Example

```python import xarray as xr air = xr.tutorial.open_dataset('air_temperature').load().air xr.options.plotting.backend = 'holoviews'

air.isel(time=500).plot() ``` 

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/3553/reactions",
    "total_count": 3,
    "+1": 3,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     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]);