Accommodate OutOfBoundsTimedelta error when decoding times
#6717
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spencerkclark
force-pushed
the
OutOfBoundsTimedelta
branch
from
4ad9967
to
c6045d6
Compare
|
Thanks @spencerkclark ! All cftime failures look to be fixed. |
dcherian
approved these changes
Jun 23, 2022
andersy005
approved these changes
Jun 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The development version of pandas raises an
OutOfBoundsTimedeltaerror instead of anOverflowErrorinpd.to_timedeltaif the timedelta cannot be represented with nanosecond precision. Therefore we must also be ready to catch that when decoding times.The
OutOfBoundsTimedeltaexception was added in pandas version 1.1, which is prior to our current minimum version (1.2), so it should be safe to import without a version check.whats-new.rst