XZise added a comment.
Well everything we don't deprecate until 2.0 will be also in 3.0 so still in 3.0 some names would need to be guessed. Is it `get_redirect_target`, `getredirecttarget` or `getRedirectTarget`? And as soon as `getRedirectTarget` is deprecated it just could call `get_redirect_target` and if that call fails at some point because of an update, `get_redirect_target` has been broken anyway.
I can agree with private stuff, because those aren't in the official API so renaming them shouldn't be a problem. With scripts it depends if they are packaged, but even when I don't have a problem if those aren't compliant. And I might be okay with some names if they are directly connected with the API. But apart from that it should be consistent, including the arguments because there is the same guessing problem. For example `Page.getVersionHistory` has a parameter `reverseOrder`, so there we could fix both in one step: Just deprecate the method and call the newly added method `get_version_history` which now has `reverse` (or `reverse_order`).
TASK DETAIL https://phabricator.wikimedia.org/T85328
REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>.
EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: jayvdb, XZise Cc: Aklapper, jayvdb, XZise, Xqt, pywikipedia-bugs