issue_comments: 277549355
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/1058#issuecomment-277549355 | https://api.github.com/repos/pydata/xarray/issues/1058 | 277549355 | MDEyOklzc3VlQ29tbWVudDI3NzU0OTM1NQ== | 1217238 | 2017-02-05T21:06:19Z | 2017-02-05T21:06:19Z | MEMBER | @crusaderky Yes, I think it could be reasonable to unify array types when you call If your scalar array is the result of an expensive dask calculation, this also might be a good use case for dask's new |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
184722754 |