issue_comments: 316376598
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/1482#issuecomment-316376598 | https://api.github.com/repos/pydata/xarray/issues/1482 | 316376598 | MDEyOklzc3VlQ29tbWVudDMxNjM3NjU5OA== | 4992424 | 2017-07-19T12:54:30Z | 2017-07-19T12:54:30Z | NONE | @mitar it depends on your data/application, right? But that information would also be helpful in figuring out alternative pathways. If you're always going to process the images individually or sequentially, then what advantage is there (aside from convenience) of dumping them in some giant array with forced dimensions/shape per slice? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
243964948 |