> There are also several PyArg_ParseTuple-using functions that have the 
> same kind of name mismatch, but since the names don't really mean 
> anything on the Python side when they're positional-only, I don't feel 
> too bad about changing them to make them make sense (or to avoid churn).

Although now is a good time to ensure sensible argument names (I usually look at the docs to find the documented ones), so that switching the function to keyword arg support is basically just a removal of '/'.