pull_requests: 1821982214
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1821982214 | PR_kwDOAMm_X85smT4G | 8942 | open | 0 | WIP: Support calendar-specific `cftime.datetime` instances | 6628425 | <!-- Feel free to remove check-list items aren't relevant to your change --> Since cftime version 1.3.0, the base `cftime.datetime` object can be calendar-aware, obviating the need for calendar-specific subclasses like `cftime.DatetimeNoLeap`. This PR aims to finally enable the use of these objects in xarray. We can also use this moment to remove cruft around accommodating inexact cftime datetime arithmetic, since that has been fixed since cftime version 1.2.0. The idea will be to support both for a period of time and eventually drop support for the calendar-specific subclasses. I do not think too much should need to change within xarray—the main challenge will be to see if we can maintain adequate test coverage without multiplying the number of cftime tests by two. This draft PR is at least a start towards that. - [ ] Closes #4336 - [ ] Closes #4853 - [ ] Closes #5551 - [ ] Closes #8298 - [ ] Closes #8941 - [ ] Tests added - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [ ] New functions/methods are listed in `api.rst` | 2024-04-14T14:33:06Z | 2024-04-14T15:41:08Z | 276893d4870bd56f0cd9ee9e60c55ac30c8f9902 | 1 | 73f35b182724503c04be99d29e691ead2e51b768 | b004af5174a4b0e32519df792a4f625d5548a9f0 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/8942 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests