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/7463#issuecomment-1428391853,https://api.github.com/repos/pydata/xarray/issues/7463,1428391853,IC_kwDOAMm_X85VI4et,2448579,2023-02-13T17:47:22Z,2023-02-13T17:47:22Z,MEMBER,"> whether we should continue allowing IndexVariable data be updated in place via .data property. IMO we should really deprecate it

I agree. We don't allow it on `.values` anyway for this reason.

Now I see we already did this in https://github.com/pydata/xarray/pull/3862/files So I guess that got lost in the indexes refactor.

> whether deep=True should deep copy the Xarray index objects

I would expect `deep=True` to deep-copy absolutely everything. That said if the Index objects are immutable then it doesn't matter?

On that pandas thread I see:
>  discovered that even if the id of the index was different on the copy, modifying the `cp.index.to_numpy()` values was corrupting the original.

Seems like we should all be setting the numpy data to be read-only with `array.flags.WRITEABLE = False`","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1550792876