pull_requests: 14261147
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
14261147 | MDExOlB1bGxSZXF1ZXN0MTQyNjExNDc= | 88 | closed | 0 | ENH: Better Dataset repr | 1217238 | @toddsmall and @hdail both reported surprise that the order of dimensions as printed in a Dataset's string representation are not necessarily the same as the order of any variable dimensions. This patch alters `Dataset.__repr__` so the order of the dimensions for each variable is now printed. Hopefully this should make things clearer. Example of the new look: ``` <xray.Dataset> Dimensions: (dim1: 100, dim2: 50, dim3: 10, time: 20) Coordinates: dim1 X dim2 X dim3 X time X Noncoordinates: var1 0 1 var2 0 1 var3 1 0 Attributes: Empty ``` Vs. the old look: ``` <xray.Dataset> Coordinates: (dim1: 100, dim2: 50, dim3: 10, time: 20) Non-coordinates: var1 X X - - var2 X X - - var3 X - X - Attributes: Empty ``` I added Coordinates to make it clear that these are items in the Dataset. I removed the dashes `-` because they added visual noise that made it harder to read the axis numbers. Note: the commits for this PR are applied on top of those for #83, so they can be merged sequentially without the need to rebase. | 2014-04-02T03:24:50Z | 2014-06-12T17:29:15Z | 2014-04-09T03:15:49Z | 2014-04-09T03:15:49Z | a31aa6429a8151300f34ccde2ad41837352da662 | 0 | 1c314febd0f2839d0f555928cf96033513113aa6 | 68e785b90fe43131c9ad23086cffacc9abcfa41c | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/88 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests