issue_comments: 279515654
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/1262#issuecomment-279515654 | https://api.github.com/repos/pydata/xarray/issues/1262 | 279515654 | MDEyOklzc3VlQ29tbWVudDI3OTUxNTY1NA== | 306380 | 2017-02-13T20:41:50Z | 2017-02-13T20:41:50Z | MEMBER | To be clear, my original question was more ambitious. It may be interpreted as "should such a system be integrated directly into the XArray codebase?" The answer of "No, it should be a standalone library that XArray wraps much in the same way it wraps around numpy or dask.array" if fine with me. Just asking. Benefits in favor would be that I suspect XArray already has mechanisms for coercion and such and it would reduce the number of total libraries. Argument against is that XArray is currently only focused on indexed and labeled arrays, and possible it doesn't want to deal with the dtype mess. So, more broadly, the question is "What is the scope of XArray?" |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
207021356 |