C API: Rename _PyUnstable_GetUnaryIntrinsicName() to PyUnstable_GetUnaryIntrinsicName()?

[vstinner]

Python 3.13 added _PyUnstable_GetUnaryIntrinsicName() and _PyUnstable_GetBinaryIntrinsicName() to the C API. I don't get the _PyUnstable prefix: PEP 689 – Unstable C API tier uses PyUnstable_ prefix.

Is it just a typo, or is the API private on purpose? If it's private, why does its name look like as if it's part of the Unstable C API?

cc @brandtbucher @iritkatriel @encukou

Linked PRs

• gh-107149: Make PyUnstable_ExecutableKinds public #108440
• gh-107149: Rename _PyUnstable_GetUnaryIntrinsicName() function #108441
• gh-107149: Rename PyUnstable_ExecutableKinds to _Py_ExecutableKinds #108651
• gh-107149: make new opcode util functions private rather than public and unstable #112042

[iritkatriel]

I doubt there was a reason for the _. Probably just a habit.