-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: After upgrading the version, unlike the api of v1.2.3, closed
was replaced by inclusive
, which led to different results
#46526
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
Comments
I just tried your example and it works fine:
could you clarify what you think the bug is, and put a descriptive title? |
This has no descriptive title, nor is the issue clearly stated, and the example seems to work fine. Closing for now. Please re-open when more info and description is available, thank you. |
closed
was replaced by inclusive
, which led to different results
This is different from the previous comparison, it may be a logical problem |
what's different?
|
ah, I see what you mean, in 1.2.3 the output was different:
|
looks like this was changed intentionally in #43394 , so no action needed here |
Pandas version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
Version 1.2.3 is OK with Argument
closed
Argument
closed
is deprecated in Version 1.4.1Expected Behavior
Empty DataFrame
Columns: [0]
Index: []
Installed Versions
V1.4.1
The text was updated successfully, but these errors were encountered: