BUG: Timedelta from Tick offsets now behaves like keyword arguments (GH#62310) #62321
+58
−3
Conversation
This file contains hidden or 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
skalwaghe-56
force-pushed
the
fix-issue-62310
branch
from
e16983f to
9189271
Compare
simonjayhawkins
added
Numeric Operations
Closed
3 tasks
|
Dupe of #53643 |
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.
pd.Timedeltaconstructed from hour offset gives wrong results #62310 (Replace xxxx with the GitHub issue number)doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.Fix Timedelta from Tick offsets (e.g.,
Timedelta(offsets.Hour(1))) giving wrong arithmetic. Hour, Minute, and Second offsets now behave like keyword arguments. Added a test to ensure consistency.Thanks!