issue_comments: 212979439
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/439#issuecomment-212979439 | https://api.github.com/repos/pydata/xarray/issues/439 | 212979439 | MDEyOklzc3VlQ29tbWVudDIxMjk3OTQzOQ== | 1217238 | 2016-04-21T15:43:27Z | 2016-04-21T15:43:27Z | MEMBER | The good news is that I fixed this display bug upstream in NumPy 1.11, which came out last month. If you upgrade to NumPy 1.11, datetimes are always treated as timezone naive. So I think we can actually consider this issue fixed. |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
89866276 |