On Jan 28, 2022, at 09:00, Steve Dower <email@example.com> 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.
Python-Dev mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Message archived at https://firstname.lastname@example.org/message/ABFHYMUHQXKMFSBGYMFHKTGHBYJN3XJF/
Code of Conduct: http://python.org/psf/codeofconduct/