issues

Table actions

1 row where user = 2086210 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
1158661615 I_kwDOAMm_X85FD8Xv 6327 Why must lat=slice() arguments be decreasing? brianmapes 2086210 closed 0     2 2022-03-03T17:00:46Z 2022-03-03T17:18:42Z 2022-03-03T17:18:29Z NONE      

What is your issue?

Many meteorological grids seem to have latitude decreasing. I am constantly forgetting this, and getting garbled results when I use slice(lat1,lat2). I can't think of any use case for which this slice ordering needs to be such a pitfall. Couldn't slice.py be set up to return the indicated interval, no matter which order the arguments are passed?

Would any user have any meaningful analysis fail if this convenience were programmed in to slice.py?

"Indexing axes with monotonic decreasing labels also works, as long as the slice or .loc arguments are also decreasing"

(Forgive a first-timer if this is the wrong place/format for this question. I searched past issues for slice and order and found no existing issue.)

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