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/2233#issuecomment-1078695337,https://api.github.com/repos/pydata/xarray/issues/2233,1078695337,IC_kwDOAMm_X85AS5Wp,1217238,2022-03-25T06:20:10Z,2022-03-25T06:20:10Z,MEMBER,"This is the second follow-up item in https://github.com/pydata/xarray/issues/6293

I think we could definitely experiment with relaxing this constraint now, although ideally we would continue to check off auditing all of the methods in that long list first.","{""total_count"": 4, ""+1"": 4, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,332471780
https://github.com/pydata/xarray/issues/2233#issuecomment-397370518,https://api.github.com/repos/pydata/xarray/issues/2233,397370518,MDEyOklzc3VlQ29tbWVudDM5NzM3MDUxOA==,1217238,2018-06-14T17:12:35Z,2018-06-14T17:12:35Z,MEMBER,"We currently enforce the requirement that non-1D variable cannot be assigned in a Dataset with a name that matches one of their dimensions. This is somewhat useful, because it means that `dataset.variables[dim]` is guaranteed to be a 1D set of coordinate labels, in the form of a `xarray.IndexVariable` backed by a `pandas.Index`.

It might make sense to relax this requirements part of the eventual ""explicit indexes"" refactor (https://github.com/pydata/xarray/issues/1603). Then the right way to get out an index will simply be `dataset.indexes[dim]` (which may or may not exist). However, this would definitely be a breaking change: it is likely that at least some code (inside and outside xarray) relies on this assumption.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,332471780