issue_comments: 185796850
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/767#issuecomment-185796850 | https://api.github.com/repos/pydata/xarray/issues/767 | 185796850 | MDEyOklzc3VlQ29tbWVudDE4NTc5Njg1MA== | 1217238 | 2016-02-18T16:16:00Z | 2016-02-18T16:16:00Z | MEMBER | This is a really good point that honestly I had not thought carefully about before. I agree that it would be very nice to have this behavior, though. This will require a bit of internal refactoring to pass on the level information to the MultiIndex during indexing. To remove unused levels after unstacking, you need to add an explicit I raised another issue for the bug related to copying MultiIndex that you had in the earlier version of this PR (#769). More broadly, if you care about MultiIndex support, it would be great to get some help pushing it. I'm happy to answer questions, but I'm at a new job and don't have a lot of time to work on new development. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
134359597 |