issue_comments: 435336049
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/pydata/xarray/issues/2159#issuecomment-435336049 | https://api.github.com/repos/pydata/xarray/issues/2159 | 435336049 | MDEyOklzc3VlQ29tbWVudDQzNTMzNjA0OQ== | 35968931 | 2018-11-02T10:29:24Z | 2018-11-02T11:07:17Z | MEMBER | I was thinking about the general solution to this problem again and wanted to clarify some things. Currently I think that any general multi-dimensional version of the 1) If possible use the values in the dimension indexes to arrange the datasets so that the indexes are monotonic, 2) Else issue a warning that some of the indexes supplied are not monotonic, 3) Then instead concatenate the supplied datasets in the order supplied (for some N-dimensional definition of "order"). The warning should tell the user that's what it's doing. This approach would then be backwards-compatible, accommodate users whose data does not have monotonic indexes (they would just have to arrange their datasets into the correct order themselves first), while still doing the obviously correct thing in unambiguous cases. However this would mean that users wanting to do a multi-dimensional Also I'm assuming we are not going to provide functionality to handle uneven sub-lists, e.g. Edit:I've just realised that there is a lot of related discussion in #2039, #1385, & #1823. I suppose what I'm suggesting here is essentially the N-D generalisation of the approach discussed in those issues, namely an extra argument |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
324350248 |