issue_comments: 36196139
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/25#issuecomment-36196139 | https://api.github.com/repos/pydata/xarray/issues/25 | 36196139 | MDEyOklzc3VlQ29tbWVudDM2MTk2MTM5 | 1794715 | 2014-02-27T00:28:13Z | 2014-02-27T00:28:13Z | CONTRIBUTOR | Agreed. I would avoid that kind of thing too. Maybe a stern warning for all conflicting attributes, and saying that they will be dropped from the new variable. For units specifically, Python has a variety of unit libraries that wrap numpy arrays and can probably do some magic. Not sure if we really want to do that, though. On Wed, Feb 26, 2014 at 4:07 PM, Stephan Hoyer notifications@github.comwrote:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
28376794 |