Implement time_unit
option for decode_cf_timedelta
#3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My main remaining concern with pydata#9618 is that timedelta decoding / encoding is inconsistent with what is done for datetimes, i.e.:
time_unit
, which would be a breaking change, e.g.:I have not yet gone the step of exposing the option to change the
time_unit
throughCFTimedeltaCoder
through thedecode_timedelta
argument, but this PR implements what I think is needed to bring the internals of non-nanosecond timedelta decoding / encoding up to speed with datetime decoding / encoding (I can do that later if you want).Similar to datetime decoding, the default behavior is to always return nanosecond resolution values, or raise an error if this would lead to overflow. As in datetime decoding, if a
time_unit
is specified that is coarser than the encoded timedeltas, thetime_unit
is updated to prevent precision loss.I added a few tests, which exercise this aspect of the code, including some that check overflow-safety and others that check we can accurately roundtrip large timedeltas. With these changes the above examples work as expected: