GeezerVison is showing github.com — C API: Rename _PyUnstable_GetUnaryIntrinsicName() to PyUnstable_GetUnaryIntrinsicName()? · Issue #107149 · python/cpython
C API: Rename _PyUnstable_GetUnaryIntrinsicName() to PyUnstable_GetUnaryIntrinsicName()? #107149DescriptionPython 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
Activityiritkatriel commented on Aug 28, 2023 I doubt there was a reason for the _. Probably just a habit. vstinner commented on Aug 31, 2023 At the end, all APIs discussed here are public and exposed with the PyUnstable prefix in the public C API (in Include/cpython/). encukou commented on Aug 31, 2023 Unstable API needs documentation and tests. Reacted by Erlend E. Aasland vstinner commented on Nov 8, 2023 iritkatriel commented on Nov 12, 2023
@erlend-aasland:
Perhaps #105481 (which added the APIs in question) should be reopened instead.
Ok, I closed this issue and reopened gh-105481 instead.
It's not easy to see on that issue what you mean (which unstable APIs? That issue contained several large PRs that change many things). I think it actually works better to finish it off on this issue or create a new one than to report a large old issue. iritkatriel commented on Nov 12, 2023 Also, PyUnstable_ExecutableKinds was not added in #105481. iritkatriel commented on Nov 13, 2023 added a commit that references this issue on Nov 14, 2023gh-107149: make new opcode util functions private rather than public … vstinner commented on Dec 15, 2023
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|