issue_comments: 443172604

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/1603#issuecomment-443172604 https://api.github.com/repos/pydata/xarray/issues/1603 443172604 MDEyOklzc3VlQ29tbWVudDQ0MzE3MjYwNA== 4160723 2018-11-30T11:14:24Z 2018-11-30T11:14:24Z MEMBER

A couple of thoughts:

If nothing useful can be done in the case of "multiple single indexes", would it make sense to discourage users explicitly creating multiple single indexes along a dimension? "Multiple single indexes" would be just a default situation when nothing specific as been defined yet or resulting from a failback.

For example, why not requiring that set_index(['x', 'y']) (with a list as argument) should always result in a multi-index regardless of the kind argument, i.e., raise if a single index is given? This is close to the current behavior, I think. This would require calling set_index for each single index that we want to (re)define, but I don't think setting a lot of single indexes at the same time is something that often happens.

Hence, would it be possible to avoid append=None and instead change the default to append=True? 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   262642978