-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
BUG fixes for date_range boundaries #56156
Conversation
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
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. |
updated and still pending review |
sorry for the delay, will try to get to it this week or next |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Sorry this has taken me a while
First, can we move this to the 2.3.0 whatsnew note please?
Second, is it possible to fix the two bugs independently?
As in, I think you can just remove the
elif end and not offset.is_on_offset(end):
# Incompatible types in assignment (expression has type "datetime",
# variable has type "Optional[Timestamp]")
end = offset.rollback(end) # type: ignore[assignment]
completely, and all existing tests will pass, as well the snippet from 56134
?
If so, I'd suggest splitting this - first, remove the unnecessary elif end
block, and then we fix the if start and not ...
one separately
ok then I'll close this, this has been picked up separately in:
Thanks |
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Fix for two issues with date_range where: