issue_comments: 154179449

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/645#issuecomment-154179449 https://api.github.com/repos/pydata/xarray/issues/645 154179449 MDEyOklzc3VlQ29tbWVudDE1NDE3OTQ0OQ== 5635139 2015-11-05T20:21:38Z 2015-11-05T20:21:38Z MEMBER

PR in for the pressing issue. It won't repr nicely, but it'll work.

Re the main issue: I think that makes sense. So we need to support dtypes that pd.Index doesn't support? If we didn't, this could all be much simpler; for example this could be the __getitem__ method (and maybe we could just have Index as a type, including MultiIndex etc):

``` python def getitem(self, key): if isinstance(key, tuple) and len(key) == 1: # unpack key so it can index a pandas.Index object (pandas.Index # objects don't like tuples) key, = key

    return self.array[key]

```

... but maybe there are data interfaces that need float32 compatibility or similar.

Re:

I'm not entirely sure what you're referring to here -- which line(s) of code is surprising you?

The unanswered question is why the code accesses the items from this coord when it's repr-ing differently, depending on the length of the other coord.

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