-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
CLN/INT: rename *possibly* -> *maybe* functions #15764
Comments
cc @gfyoung |
Seem reasonable. |
also (separately), we should rename all of the functions in |
StanczakDominik
added a commit
to StanczakDominik/pandas
that referenced
this issue
Mar 21, 2017
Also rename "private" functions in pandas.type.cast Closes pandas-dev#15764
3 tasks
Figured I would take a stab at this one. |
mattip
pushed a commit
to mattip/pandas
that referenced
this issue
Apr 3, 2017
Also rename "private" functions in pandas.type.cast closes pandas-dev#15764 Author: Dominik Stanczak <stanczakdominik@gmail.com> Closes pandas-dev#15771 from StanczakDominik/rename-possibly and squashes the following commits: 486b932 [Dominik Stanczak] Cleanup missed linting errors 188c48b [Dominik Stanczak] CLN/INT: Rename _possibly to _maybe
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
we have a mixed bag on naming this. Let's change
possibly
->maybe
. Keep everything else the same. (if you do the same search formaybe
you will fine it to be far more common). Note that the usage of these functions will have to be renamed as well :>The text was updated successfully, but these errors were encountered: