Nice Zombies

Note it's `filter='data'`. The warning message should stay but could mention this is only necessary on 3.12 & 3.13. And that you need to check this manually before that.

Reason for revert: > This PR does not address the concerns of the issue: the `METH_VARARGS` calling convention is still used. See discussion in #118012. You can skip news.

I used VS Code to detect the usage of `METH_KEYWORDS` in private functions, (but potentially exported as public). Regex `"_[a-z].*METH_KEYWORDS`, files to include `*.c.h`: ```none Modules\clinic\_asynciomodule.c.h: 1030: {"_register_task", _PyCFunction_CAST(_asyncio__register_task), METH_FASTCALL|METH_KEYWORDS,...

Is there a difference in performance between `METH_FASTCALL|METH_KEYWORDS` & `METH_O`?

> See [the C API docs](https://docs.python.org/3/c-api/structures.html#c.METH_VARARGS). Very often you will find answers to your questions in the docs; if the docs are missing information, it is a documentation bug (and...

I'll close this. It would be better to optimise `METH_VARARGS` instead, like @corona10 mentioned. Is this an idea for faster-cpython?

Wouldn't it better to convert the pull request back to a draft? GitHub automatically prevents you from merging those.

Yeah, it also allows us to link to a specific section, rather than the start of the PEP (e.g. `typing.overload`).

If intersphinx is a problem, we could maybe use canonical links for https://typing.readthedocs.io.