pull_requests: 68785473
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 68785473 | MDExOlB1bGxSZXF1ZXN0Njg3ODU0NzM= | 842 | closed | 0 | Fix #665 decode_cf_timedelta 2D | 950575 | Long time listener first time caller :wink: I am not 100% about this PR though. I think that there are cases when we need the actual data rather than the `timedelta`. In [this](http://nbviewer.jupyter.org/gist/ocefpaf/6ed33fb35fe526f677e215b3fb304847) notebook we have wave period (`'mper'`) that should be _seconds_ ranging `0-30` and not those big numpy timedelta numbers. I know that I can get that behavior with `decode_times=True` when opening the dataset, but then the `time` coordinate get decoded as well. (Maybe I am way off and there is a way to do this.) | 2016-05-03T22:26:34Z | 2016-05-14T00:36:12Z | 2016-05-04T17:11:59Z | 2016-05-04T17:11:59Z | b25d145b092e1f0ae6555e9ac2103a7afb838592 | 0 | 888e6c25d462fdd89a397c127a409775a5cc0fcf | ecc442054f05c5b500f3b58d3c9dacce75a9de36 | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/842 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests