issue_comments: 194964987
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/789#issuecomment-194964987 | https://api.github.com/repos/pydata/xarray/issues/789 | 194964987 | MDEyOklzc3VlQ29tbWVudDE5NDk2NDk4Nw== | 4295853 | 2016-03-10T17:22:11Z | 2016-03-10T17:22:11Z | CONTRIBUTOR | @jhamman and @shoyer, do you know if more general support for times will be provided? I would say this is a potential roadblock inhibiting easy adoption of this library within the climate community. For example, this is creating problems when we setup and analyze climate models (cc @akturner, @douglasjacobsen, @milenaveneziani). There are obvious work arounds, but they are hacks, e.g., I just add 1700 or some arbitrary year within my wrapper to MPAS at https://github.com/pwolfram/mpas_xarray_wrapper. However, this does not appear to be a viable long-term solution. Does anyone have some advice on how to better deal with this problem? |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
139956689 |