Skip to content

BUG: Timestamp - Timestamp should be pd.Timedelta, not datetime.timedelta #8865

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
Closed
shoyer opened this issue Nov 20, 2014 · 1 comment · Fixed by #8981
Closed

BUG: Timestamp - Timestamp should be pd.Timedelta, not datetime.timedelta #8865

shoyer opened this issue Nov 20, 2014 · 1 comment · Fixed by #8981
Labels
Bug Dtype Conversions Unexpected or buggy dtype conversions Timedelta Timedelta data type
Milestone
0.15.2

Comments

@shoyer
Copy link
Member

shoyer commented Nov 20, 2014

Currently it returns a datetime.timedelta object:

>>> pd.Timestamp('2000-01-01') - pd.Timestamp('1999-01-01')
datetime.timedelta(365)

Somewhat related: #8813
@jreback
Copy link
Contributor

jreback commented Nov 20, 2014

hmm thought this was tested
should for sure return a Timedelta

@jreback jreback added Bug Dtype Conversions Unexpected or buggy dtype conversions Timedelta Timedelta data type labels Nov 20, 2014
@jreback jreback added this to the 0.15.2 milestone Nov 20, 2014
@shoyer shoyer mentioned this issue Nov 28, 2014
Closed
@jreback jreback modified the milestones: 0.16.0, 0.15.2 Dec 3, 2014
@jreback jreback mentioned this issue Dec 3, 2014
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug Dtype Conversions Unexpected or buggy dtype conversions Timedelta Timedelta data type
Projects
None yet
Milestone
0.15.2
2 participants
@jreback @shoyer