-
Notifications
You must be signed in to change notification settings - Fork 595
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
Rename map #1795
base: master
Are you sure you want to change the base?
Rename map #1795
Conversation
updating from master
pip8 clean-up Co-authored-by: Jovan Veljanoski <jovan.veljanoski@gmail.com>
rename-fix Co-authored-by: Jovan Veljanoski <jovan.veljanoski@gmail.com>
Co-authored-by: Jovan Veljanoski <jovan.veljanoski@gmail.com>
Co-authored-by: Jovan Veljanoski <jovan.veljanoski@gmail.com>
Co-authored-by: Jovan Veljanoski <jovan.veljanoski@gmail.com>
unrelated
unrelated
Is this the same idea as #1135? I think we got stuck there on the API name, and whether the current My preference would be for a single What do you think? |
I have
I initially had the same idea. I can check if name is a dict, and then apply it. |
Yes, let's put it in a single method. |
Rename multiple columns
Simply iterate and rename columns if possible.
returns the new columns which were added.
I have created it on another function to allow backward compatibility.
We can also rename this function to
rename_columns
for example, or something else, or allow name param to be a dict inrename()
.Example:
What do you think?