On 1/28/2022 5:15 PM, Barry Warsaw wrote:
On Jan 28, 2022, at 09:00, Steve Dower <steve.do...@python.org> wrote:
Does HPy have any clear guidance or assistance for their users to keep it up to
date?
I'm concerned that if we simply substitute "support the C API for everyone" with
"support the C API for every version of HPy" we're no better off.
Will it ever make sense to pull HPy into the CPython repo so that they evolve
together? I can see advantages and disadvantages. If there’s a point in the
future where we can just start promoting HPy as an official alternative C API,
then it will likely get more traction over time. The disadvantage is that HPy
would evolve at the same annual pace as CPython.
Possibly, but we'd have to be really careful to not actually *evolve*
HPy. It would essentially be a new stable API, but ideally one that uses
all the preprocessor tricks we can (and perhaps runtime tricks) to
compile against any CPython version rather than just the one that it
comes with.
PSF "ownership" is probably enough to make it official (for those people
who need everything to be "official"). I don't think that's necessary,
but it does smooth the path for some people to be willing to use it.
Cheers,
Steve
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/XCJH743KWSZ6436PU7RLG4NCX62ELTPR/
Code of Conduct: http://python.org/psf/codeofconduct/
