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/7515#issuecomment-1423274243,https://api.github.com/repos/pydata/xarray/issues/7515,1423274243,IC_kwDOAMm_X85U1XED,971601,2023-02-08T21:39:47Z,2023-02-08T21:39:47Z,NONE,"> This tells me there is a bit of work to do at the core of Aesara's numpy compatibility. Xarray will make frequent references to attributes like `data.shape`, `data.ndim`, etc expecting to get numpy-like results.

We'll fix the compatibility issues, but we first need to understand what the expectations on something like `data.shape` should be in these circumstances.

For a shared variable, it's always possible to get a value for `data.shape` by referencing the underlying data, but the reason we don't do that by default is—in part—due to the fact that shared variables can be updated with values that have different shapes (but the same dtypes and number of dimensions).","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1575494367
https://github.com/pydata/xarray/issues/7515#issuecomment-1422995401,https://api.github.com/repos/pydata/xarray/issues/7515,1422995401,IC_kwDOAMm_X85U0S_J,3885044,2023-02-08T17:35:41Z,2023-02-08T17:35:41Z,NONE,"Aesara has a NumPy-like API, and we always planned to conform to the python array api standard (see https://github.com/aesara-devs/aesara/issues/729 for instance). This would be the impetus for us to do it now.","{""total_count"": 4, ""+1"": 4, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1575494367
https://github.com/pydata/xarray/issues/7515#issuecomment-1422043601,https://api.github.com/repos/pydata/xarray/issues/7515,1422043601,IC_kwDOAMm_X85UwqnR,971601,2023-02-08T05:36:53Z,2023-02-08T06:32:37Z,NONE,"> @jhamman Yes, I think this is an interesting discussion to have. We actually want to add named dimensions and coordinates to PyTensor (a fork of aesara): https://github.com/pymc-devs/pytensor, adding this capability was one of the reasons for forking, as PyMC already has some support built-in (coords and dims) and uses xarray in various places. Tighter integration between the two is a great goal.

Hi, I'm the creator and maintainer of Aesara and we _are_ interested in discussing named dimensions and arrays.

We don't know why @twiecki and his PyMC Labs group have been attempting to implicitly speak for us on this—or any other—matter.  As you can see, the original issue in Aesara is still open, and we have **not** said that the feature cannot be implemented in some way.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1575494367
https://github.com/pydata/xarray/issues/7515#issuecomment-1422075564,https://api.github.com/repos/pydata/xarray/issues/7515,1422075564,IC_kwDOAMm_X85Uwyas,3885044,2023-02-08T06:18:38Z,2023-02-08T06:29:26Z,NONE,"Author of the little diagram and core member of Aesara here 🙂 If you want to know a little more about where the project is headed you can consult the project’s [Mission statement](https://github.com/aesara-devs/aesara/blob/main/doc/mission.rst). Happy to chat, you can find my contact info on my GitHub profile, and/or join our new [Discord server](https://discord.gg/h3sjmPYuGJ).","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1575494367