issue_comments: 43359850
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/131#issuecomment-43359850 | https://api.github.com/repos/pydata/xarray/issues/131 | 43359850 | MDEyOklzc3VlQ29tbWVudDQzMzU5ODUw | 2443309 | 2014-05-16T17:49:14Z | 2014-05-16T17:49:14Z | MEMBER | Both NCO and CDO keep all attributes, and as you mention, maintain a history attribute. Even for operations like "variance" where the units are no longer accurate. Maybe we're headed to a user specified option to keep the attributes around with the default being option 1. I can see this existing at any (but probably not all) of these levels:
- module ( This approach would put the onus on the user to specify they want to keep metadata around. My preference would be to apply this at the module level. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
33637243 |