issue_comments: 36279915
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/26#issuecomment-36279915 | https://api.github.com/repos/pydata/xarray/issues/26 | 36279915 | MDEyOklzc3VlQ29tbWVudDM2Mjc5OTE1 | 514053 | 2014-02-27T19:20:25Z | 2014-02-27T19:20:25Z | CONTRIBUTOR | Yeah I think keeping them transparent to the user except when reading/writing is the way to go. Two datasets with the same data but different encodings should still be equal when compared, and operations beyond slicing should probably destroy encodings. Not sure how to handle the various file formats, like you said it could be all part of the store, or we could just throw warnings/fail if encodings aren't feasible. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
28445412 |