Skip to content

Is it OK to remove _PyObject_Vectorcall? #212

Description

@encukou

PEP-590 says:

The underscore in the names _PyObject_Vectorcall and _Py_TPFLAGS_HAVE_VECTORCALL indicates that this API may change in minor Python versions. When finalized (which is planned for Python 3.9), they will be renamed to PyObject_Vectorcall and Py_TPFLAGS_HAVE_VECTORCALL. The old underscore-prefixed names will remain available as aliases.

I'm not aware of a decision to override the PEP. But the reasoning behind the changes is scattered in a maze of issues, PRs and topics that were never collected into a PEP, so it's very possible that I'm missing something. (It seems @vstinner is in charge of the removals, but I don't know where to ask or discuss -- see e.g. here).

The question I want to ask is practically intractable at this point, so I'll ask a simple one instead:
Does the SC think that it is OK to remove _PyObject_Vectorcall without a change to PEP-590, new PEP, or SC decision?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions