issue_comments

Table actions

2 rows where issue = 1575494367 and user = 971601 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • brandonwillard · 2 ✖

issue 1

  • Aesara as an array backend in Xarray · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1423274243 https://github.com/pydata/xarray/issues/7515#issuecomment-1423274243 https://api.github.com/repos/pydata/xarray/issues/7515 IC_kwDOAMm_X85U1XED brandonwillard 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
}
   Aesara as an array backend in Xarray 1575494367
1422043601 https://github.com/pydata/xarray/issues/7515#issuecomment-1422043601 https://api.github.com/repos/pydata/xarray/issues/7515 IC_kwDOAMm_X85UwqnR brandonwillard 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
}
   Aesara as an array backend in Xarray 1575494367

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);