issue_comments: 1534695467
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/3213#issuecomment-1534695467 | https://api.github.com/repos/pydata/xarray/issues/3213 | 1534695467 | IC_kwDOAMm_X85beZgr | 1634164 | 2023-05-04T12:31:22Z | 2023-05-04T12:31:22Z | NONE | That's a totally valid scope limitation for the sparse package, and I understand the motivation. I'm just saying that the principle of least astonishment is not being followed: the user cannot at the moment read either the xarray or sparse docs and know which portions of the xarray API will work when giving |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
479942077 |