issues

Table actions

1 row where "closed_at" is on date 2018-05-08, comments = 4 and repo = 13221727 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

  • xarray · 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
319985789 MDExOlB1bGxSZXF1ZXN0MTg1NzY2MTg3 2101 DOC: Add resample e.g. Edit rolling e.g. Add groupby e.g. raybellwaves 17162724 closed 0     4 2018-05-03T16:08:48Z 2018-05-08T15:46:17Z 2018-05-08T04:23:03Z CONTRIBUTOR   0 pydata/xarray/pulls/2101
  • [NA] Closes #xxxx (remove if there is no corresponding issue, which should only be the case for minor changes)
  • [NA] Tests added (for all bug fixes or enhancements)
  • [NA] Tests passed (for all non-documentation changes)
  • [NA] Fully documented, including whats-new.rst for all changes and api.rst for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later)

Added a resample example to reflect the DeprecationWarning: .resample() has been modified to defer calculations. Instead of passing 'dim' and 'how="mean", instead consider using.... There were also some missing parameters in the docs.

Made a minor edit to my rolling example which uses the parameter center. I can't remember if that parameter was there last time but I think it's useful to return the time value for the middle of window.

Added a groupby example. Not sure if this should go here. See text below for my motivation of putting an example in the docstring of the class/object.

I learnt xarray before I learnt pandas so these example will hopefully be useful to other beginners as it took me a minute to get the syntax right.

Whilst there are great examples of these functions in the docs, a google search of a function for example xarray rolling often returns the doc entry that that object. Having a little example there is helpful for me to get the syntax right. The key/value pair in a dictionary for example is very powerful and always takes me a few tries to get the entry right.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2101/reactions",
    "total_count": 1,
    "+1": 1,
    "-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]);