issue_comments: 1423274243

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/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