Georg Brandl added the comment: > 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 '/'. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20227> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
