BUG: Timestamp with unit=Y or unit=M #47266
Merged
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
5 tasks
mroeschke
reviewed
Jun 7, 2022
pandas/_libs/tslibs/conversion.pyx
Outdated
| if unit in ["Y", "M"]: | ||
| # GH#47266 cast_from_unit leads to weird results e.g. with "Y" | ||
| # and 150 we'd get 2120-01-01 09:00:00 | ||
| ts = np.datetime64(ts, unit.upper()) |
There was a problem hiding this comment.
Nit: Is the upper needed? The units in the if check are already uppered
There was a problem hiding this comment.
good point, will update
mroeschke
approved these changes
Jun 7, 2022
yehoshuadimarsky
pushed a commit
to yehoshuadimarsky/pandas
that referenced
this pull request
Jul 13, 2022
* BUG: Timestamp with unit=Y or unit=M * GH refs * remove unnecessary upper
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.
doc/source/whatsnew/vX.X.X.rstfile if fixing a bug or adding a new feature.