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/1492#issuecomment-318788600,https://api.github.com/repos/pydata/xarray/issues/1492,318788600,MDEyOklzc3VlQ29tbWVudDMxODc4ODYwMA==,1217238,2017-07-29T00:11:49Z,2017-07-29T00:12:04Z,MEMBER,"To be honest, this wasn't entirely intentional: I didn't think about the difference in slice handling conventions between labeled and unlabeled arrays when we changed this in 0.9. But at this point, I would be loathe to change it.

I suppose this is also an argument in favor of changing the slice convention we copied from pandas to exclusive rather than inclusive of upper bounds.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,245778442
https://github.com/pydata/xarray/issues/1492#issuecomment-318774938,https://api.github.com/repos/pydata/xarray/issues/1492,318774938,MDEyOklzc3VlQ29tbWVudDMxODc3NDkzOA==,4160723,2017-07-28T22:17:40Z,2017-07-28T22:17:40Z,MEMBER,"> Maybe slicing uses the standard (excluding) python slice() for these dimensions and continues to use the (including) pandas slice for coordinates?

Yes, this is what xarray does since 0.9. From the indexing section of the documentation:

> Label based indexing with .sel and .loc uses standard positional, integer-based indexing as a fallback for dimensions without a coordinate label.

To fix your scripts you have to choose between set range coordinates or update the slice values.  


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