pull_requests: 625530046

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
625530046 MDExOlB1bGxSZXF1ZXN0NjI1NTMwMDQ2 5233 closed 0 Calendar utilities 20629530 <!-- Feel free to remove check-list items aren't relevant to your change --> - [x] Closes #5155 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [x] New functions/methods are listed in `api.rst` So: - Added `coding.cftime_offsets.date_range` and `coding.cftime_offsets.date_range_like` The first simply swtiches between `pd.date_range` and `xarray.cftime_range` according to the arguments. The second infers start, end and freq from an existing datetime array and returns a similar range in another calendar. - Added `coding/calendar_ops.py` with `convert_calendar` and `interp_calendar` Didn't know where to put them, so there they are. - Added `DataArray.dt.calendar`. When the datetime objects are backed by numpy, it always return `"proleptic_gregorian"`. I'm not sure where to expose the function. Should the range-generators be accessible directly like `xr.date_range`? The `convert_calendar` and `interp_calendar` could be implemented as methods of `DataArray` and `Dataset`, should I do that? 2021-04-28T20:01:33Z 2021-12-30T22:54:49Z 2021-12-30T22:54:11Z 2021-12-30T22:54:11Z b14e2d8400da5c036f1ebb5486939f7f587b9f27     0 5aa747079ce32c51645ca245b1423cbacaf0cb1b 2694046c748a51125de6d460073635f1d789958e CONTRIBUTOR   13221727 https://github.com/pydata/xarray/pull/5233  

Links from other tables