some improvements regarding pandas 2.2.x futurewarnings and error raises #2477
+44
−17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KS-HTK
approved these changes
Dec 5, 2024
|
@SteffenMeinecke I think this is a good approach. Would you mind adding a test? |
I fear, I won't have time in the near future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@vogt31337 @KS-HTK @mfranz13 I guess we have not yet started to fix the 2.2.x FutureWarnings for pandas 3 behavior. Here, I started for that short time I had. You can have a look and comment on whether you like my proposal to concat DataFrames with
empty_defaults_per_dtype()or not. Regarding the FutureWarning offillna()andreplace(), I like to reference this post which helped me a lot.