hai shi <shihai1...@126.com> added the comment:
> You always can use PyObject_CallMethod(). It is not a method called in tight > loop for which the overhead of calling method is significant. Thanks, serhiy. You are right. To PR19069, it's fine to use `PyList_SetSlice` or `PyObject_CallMethod`. We don't have the enough reason to add `PyList_Remove()`,so I decided close this bpo now. PS: I attach a PR which have add `PyList_Remove` in here in case we will meet another appropriate user case somedays: https://github.com/python/cpython/compare/master...shihai1991:add_PyList_Remove?expand=1 ---------- resolution: -> rejected stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41871> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
