Skip to content

Updating and re-opening PR #48275 #50542

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.

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

Closed
wants to merge 8 commits into from
Closed

Conversation

srotondo
Copy link
Contributor

@srotondo srotondo commented Jan 3, 2023

@srotondo
Copy link
Contributor Author

srotondo commented Jan 3, 2023

Mistyped the issue number in that commit message, should be #47953.

tm.assert_series_equal(resultarray1, expectedarray)
tm.assert_series_equal(resultarray2, expectedarray)

df = DataFrame({"T": [Timestamp("2019-04-30")], "D": [DateOffset(months=1)]})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a separate test.

@gfyoung gfyoung added Bug Timestamp pd.Timestamp and associated methods Timedelta Timedelta data type labels Jan 7, 2023
Copy link
Member

@MarcoGorelli MarcoGorelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @srotondo for working on this!

The change looks fine to me, if you address the comments on tests I think we can get this in

Comment on lines +1070 to +1071
startscalar = Timestamp("2020-01-30")
startarray = Series([Timestamp("2020-01-30")])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could these be parametrised over?

}
)
frameresult2 = df2["T"] + 26 * df2["D"]
assert frameresult1[0] == frameresult2[0]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any chance they could both be checked against some expected output? otherwise perhaps in the future they could both change and become wrong?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I can do that. I haven't had much time to work on this recently, but I'll try to handle all these comments when I find some time to deal with them.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, no hurry, thanks!

@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2023

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

@github-actions github-actions bot added the Stale label Mar 6, 2023
@srotondo
Copy link
Contributor Author

srotondo commented Mar 8, 2023

Sorry this went stale, I've been really busy lately, I think I'll be able to find time to clean this up soon.

@mroeschke
Copy link
Member

Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Stale Timedelta Timedelta data type Timestamp pd.Timestamp and associated methods
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: inconsistent behavior of DateOffset
5 participants