issue_comments: 418778596
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/2399#issuecomment-418778596 | https://api.github.com/repos/pydata/xarray/issues/2399 | 418778596 | MDEyOklzc3VlQ29tbWVudDQxODc3ODU5Ng== | 1217238 | 2018-09-05T15:41:21Z | 2018-09-05T15:41:21Z | MEMBER | Thanks for the report! This was actually a somewhat intentional omission in xarray, but if would not be particularly difficult to add in this feature if we want it. At the very least, we should note this deviation somewhere in the docs. There are two potentially problematic aspects to the pandas behavior:
1. It means that you cannot count on indexing a dataframe with its own index to return something equivalent to the original dataframe, e.g., consider Now that you bring this up, I wonder how the existing supporting for indexing like |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
357156174 |