-
Notifications
You must be signed in to change notification settings - Fork 92
Adding dict support for renaming columns #671
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
Open
henrydingliu
wants to merge
1
commit into
casact:master
Choose a base branch
from
henrydingliu:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
Not sure if I understood this comment. To me it seems to be testing 2 things at once, trying to map a new name to a non-existing column, and attempting to do a rename meant for columns, but accidentally applied to the origin instead, and then alerting the user by raising an error.
However, doing something similar in pandas doesn't actually cause an error. For example, if we create a DataFrame with columns
AandBbut pass a mapping{'C': 'bar'}whose key not only does not match either column but also gets accidentally passed to theindexparameter, we just get a copy of the original DataFrame with no error.I believe this was intentional by design for pandas, for example if we want to apply a mapping where a DataFrame only hit a subset of the keys (or even none), we'd still want it to work.
Eventually, to match the functionality of
DataFrame.rename, we'll need to remove thevalueparameter and supply the mapping to other parameters, working our way towards matching the signature ofDataFrame.rename:DataFrame.rename(mapper=None, *, index=None, columns=None, axis=None, copy=<no_default>, inplace=False, level=None, errors='ignore')But I remember we talked about moving these further changes to other issues. This PR still makes sense given the chainladder's current behavior, so I can approve this as long as we're aligned that the function's signature will change to match
DataFrame.rename(or get as close as possible) in future PRs. Alternatively, if you'd like to tackle #662 in this PR, or even go all the way to get the signatures to match in this PR, I can review that 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.
i'm not following. this test was named test_rename_exception. since i added a new exception to the rename function, I added a clause to test the new exception.
what would you like to see changed?