pull_requests: 61156349
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 61156349 | MDExOlB1bGxSZXF1ZXN0NjExNTYzNDk= | 778 | closed | 0 | fix value error in data-structures doc | 10050469 | This should fix the error in the docs here: http://xarray.pydata.org/en/latest/data-structures.html It is a detail, but it occurred to me that the examples of this section don't use the (space, time) dimension order (e.g. `dims=['time', 'space']`). Most of the climate datasets I know of are using the numpy (lat, lon, time) dim order. Is it intentional? | 2016-02-29T22:21:58Z | 2016-03-01T00:50:27Z | 2016-03-01T00:50:27Z | 2016-03-01T00:50:27Z | 2661aa20e745b14291d55c0b9d7e60720ce434b3 | 0 | b8eaa7cbf6e9fc24e0b80a13301ab81baf60d303 | b15f0ee759248ef52b9a53d410090133b86216ee | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/778 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests