issues: 359307319
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 359307319 | MDU6SXNzdWUzNTkzMDczMTk= | 2411 | datetime parser different between 32bit and 64bit installations | 2656596 | closed | 0 | 2 | 2018-09-12T04:03:11Z | 2018-09-13T03:54:17Z | 2018-09-13T03:54:17Z | NONE | I just noticed that my 64bit Python 3.6 installation with xarray does not parse the datetimes correctly from a netcdf, while the 32bit version seems to work fine. There seems to be some kind of offset. Since I can't attach a netcdf to this issue, here's a link to an example netcdf file: https://drive.google.com/open?id=1WhtWmN1ZBpbsfu7q7hGy2le-nujInfkI This seems to happen for both 0.10.7 and 0.10.8. The datetime values should be hourly. Thanks! ```python import xarray as xr ms1 = xr.open_dataset(nc) print(ms1.time) ``` |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2411/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |