-
-
Notifications
You must be signed in to change notification settings - Fork 141
MAINT: Bump pandas to 1.5.0 #317
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
Conversation
1.5.0 Released this weekend. |
I think we can take the whatsnew document and create a list of all the deprecations. Can you do that in #227 with a checklist so it makes it easier to see which ones you have done and which ones are still to be done? this will make it easier for me to review. Thanks!!! |
@bashtage Not sure you saw my comment here: #317 (comment) It would be easier to review if we have a tracking list of all the 1.5 changes we need to make. Can you make such a list? |
That would definitly be the easier for reviewers :) (but going through the changelog is no fun). Later today, I will simply execute code with the removed arguments to test whether they raise warnings. It might not cover all deprecations, but I can then at least approve this PR. |
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.
A few optional comments, but otherwise looks good to me.
f1ba252
to
48cdc77
Compare
I created a list for all of the 1.5 issues (changes and deprecations) here: #227 (comment) So as they get fixed, we can edit that comment and check off the boxes and put a link to the relevant PR I'll use that list to cross-check against this PR once it turns green again. @bashtage ping me when green |
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.
Other simple ones to do with deprecations for this PR (there are more to do in a later PR):
- remove
__array_wrap__()
fromcore/generic.pyi
- Deprecated Timedelta.freq and Timedelta.is_populated
- Deprecated Timedelta.delta
Am tracking in #227 what you did here, and would need to update that if you do the above 3.
Other concern (which is marked in a few places in this review) is the deletion of tests that addressed previously reported issues with respect to groupby.__iter__()
. Please don't delete old tests (unless they are no longer relevant)
Thanks for all the work on this.
@@ -278,7 +278,7 @@ class Styler(StylerRenderer[Styler]): | |||
) -> Styler: ... | |||
def highlight_null( | |||
self, | |||
null_color: str = ..., | |||
color: str | None = ..., |
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.
docs are missing None
as an argument - can you create an issue for that?
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.
Docs on that one are pretty wrong. Have wrong color too
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.
- We're in disagreement about the deprecation of
groupby(Scalar)
. The code that was in the test suite still works without a deprecation message, so can you put back all of those changes, or prove to me otherwise. - With respect to
factorize()
, you can still include it. The error you were getting was becausemypy
doesn't allow a subclass to return a subtype of the parent's class return type.pyright
allows that. So just put a# type: ignore
incore/arrays/sparse.pyi
forfactorize
and then you should be good (with docs about why it is necessary). - For
ExcelWriter
, some methods/properties were deprecated, but there is a list of them that are now public, and you removed them. Maybe you misunderstood the list I created, so those need to be in there (e.g.,book
,sheets
, etc.)
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.
there are also still a few things I pointed out in the previous review that still have to be addressed.
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.
Let's fix the rsplit
one (it was a bug), and then this should be good to go.
Then I'll do the first 1.5.0.yymmdd release.
Think it is ready. |
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.
thanks @bashtage
No description provided.