issue_comments
5 rows where author_association = "MEMBER" and issue = 495799492 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Linear algebra support · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1101533629 | https://github.com/pydata/xarray/issues/3322#issuecomment-1101533629 | https://api.github.com/repos/pydata/xarray/issues/3322 | IC_kwDOAMm_X85BqBG9 | dcherian 2448579 | 2022-04-18T16:14:03Z | 2022-04-18T16:14:03Z | MEMBER | Closing in favour of xarray-einstats |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Linear algebra support 495799492 | |
822124811 | https://github.com/pydata/xarray/issues/3322#issuecomment-822124811 | https://api.github.com/repos/pydata/xarray/issues/3322 | MDEyOklzc3VlQ29tbWVudDgyMjEyNDgxMQ== | dcherian 2448579 | 2021-04-19T02:28:41Z | 2021-04-19T02:28:41Z | MEMBER |
Thanks @OriolAbril . This sounds like a nice xarray-contrib repo if it's general enough. Note that we do have |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Linear algebra support 495799492 | |
533765137 | https://github.com/pydata/xarray/issues/3322#issuecomment-533765137 | https://api.github.com/repos/pydata/xarray/issues/3322 | MDEyOklzc3VlQ29tbWVudDUzMzc2NTEzNw== | shoyer 1217238 | 2019-09-21T03:59:26Z | 2019-09-21T03:59:33Z | MEMBER | I think the way to write something like an LU decomposition would be to use xarray's I don't know if this could/should live in xarray proper. We tend to have pretty high standards, which slows development. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Linear algebra support 495799492 | |
533248639 | https://github.com/pydata/xarray/issues/3322#issuecomment-533248639 | https://api.github.com/repos/pydata/xarray/issues/3322 | MDEyOklzc3VlQ29tbWVudDUzMzI0ODYzOQ== | max-sixty 5635139 | 2019-09-19T18:16:04Z | 2019-09-19T18:16:04Z | MEMBER | Somewhat related: https://github.com/pydata/xarray/pull/2766 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Linear algebra support 495799492 | |
533228830 | https://github.com/pydata/xarray/issues/3322#issuecomment-533228830 | https://api.github.com/repos/pydata/xarray/issues/3322 | MDEyOklzc3VlQ29tbWVudDUzMzIyODgzMA== | crusaderky 6213168 | 2019-09-19T17:23:10Z | 2019-09-19T17:23:10Z | MEMBER | Hi @weipeng1999 , could you link the reference implementation in numpy/scipy? I think this would be niche-ish. I would personally try to keep xarray free of functionality that only a tiny fraction of the users actually use - particularly when such functionality can be implemented with a trivial wrapper by the users themselves. e.g. at the moment we have exactly one scipy function being wrapped, and that's linear interpolation which is useful to a lot of people. I think this falls into a more general discussion on how niche a function must be in order to be excluded from the library - @shoyer what's your opinion? Regardless, I would like to point you to https://xarray-extras.readthedocs.io which is a module that I created exactly for this kind of cases (PRs are welcome). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Linear algebra support 495799492 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 4