Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport PR #49579 on Branch 1.5.x (BUG: Behaviour change in 1.5.0 when using Timedelta as Enum data type) #49787

Merged
merged 1 commit into from Nov 19, 2022
Merged

Backport PR #49579 on Branch 1.5.x (BUG: Behaviour change in 1.5.0 when using Timedelta as Enum data type) #49787

merged 1 commit into from Nov 19, 2022

Conversation

phofl
Copy link
Member

@phofl phofl commented Nov 19, 2022

@krasch @phofl
BUG: Behaviour change in 1.5.0 when using Timedelta as Enum data type (…
7da0091 
…pandas-dev#49579)

* Add cls argument to _timedelta_from_value_and_reso

* Add test

* Add fix to changelog

Co-authored-by: krasch <dev@krasch.io>
(cherry picked from commit 606499d)

# Conflicts:
#	pandas/_libs/tslibs/timedeltas.pyx
#	pandas/tests/scalar/timedelta/test_constructors.py
@phofl phofl added this to the 1.5.2 milestone Nov 19, 2022
@phofl phofl changed the title Backport PR BUG: Behaviour change in 1.5.0 when using Timedelta as Enum data type Backport PR #49579 on Branch 1.5.x (BUG: Behaviour change in 1.5.0 when using Timedelta as Enum data type) Nov 19, 2022
@phofl phofl added Regression Functionality that used to work in a prior pandas version Timedelta Timedelta data type labels Nov 19, 2022
@phofl phofl merged commit 98c6139 into pandas-dev:1.5.x Nov 19, 2022
@phofl phofl deleted the backport_enum branch November 19, 2022 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Regression Functionality that used to work in a prior pandas version Timedelta Timedelta data type
Projects
None yet
Milestone
1.5.2
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@phofl @krasch