issue_comments: 279846111
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-279846111 | https://api.github.com/repos/pydata/xarray/issues/1262 | 279846111 | MDEyOklzc3VlQ29tbWVudDI3OTg0NjExMQ== | 1217238 | 2017-02-14T21:46:09Z | 2017-02-14T21:46:09Z | MEMBER | CC @pydata/xarray in case anyone else has opinions here
We really don't have much existing machinery. Two things we have that might be useful:
Fewer libraries is definitely nice, but I see this as more of a secondary rather than primary goal. More broadly, doing this project right will need strong separation of concerns from xarray's handling of labeled arrays. So there's not a huge amount to be gained by doing it in the same repository.
I would love to see this project be successful and integrated with xarray. But better dtypes is tangental to our current focus, and project maintenance is already stretched pretty thin -- there's still a lot of core functionality to build out for manipulation of labeled arrays. So I'm not comfortable with building this in xarray at this time. But I would be happy to revisit this decision when you have a design document, prototype and someone committed to developing and maintaining the module. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
207021356 |