issues: 1158661615
This data as json
| 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? | 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 | 13221727 | issue |