Fix pandas chained fillna deprecations - #56
Open
utsinboots wants to merge 1 commit into
Open
Conversation
(cherry picked from commit ddacd96814036b902154e9b0067f2983c74f9a34)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Ports the remaining applicable change from a fix previously merged in MUIOGO.
fillna(..., inplace=True)operation with direct assignment to avoid pandas chained-assignment deprecation behavior. The other replacements from the source PR are already present in MUIO.Testing
-Full results processing could not be tested because of a pre-existing CBC working-directory failure when running MUIO from a source clone. The same failure occurs on latest MUIO master.