On Sat, 30 Apr 2022, 3:02 am Guido van Rossum, <gu...@python.org> wrote:
> > I think picking "semi-stable" would be giving in to the OCD nerd in all of > us. :-) While perhaps technically less precise, "unstable" is the catchy > name with the right association. (And yes, we should keep it stable within > bugfix releases, but the name doesn't need to reflect that detail.) The > "internal API" isn't an API at all (except for CPython core developers and > contributors). The "unstable API" would definitely be an *API* for users > outside the core. > > So let's please go with "unstable". > While I've advocated for semi-stable in previous threads, I now agree the pragmatic arguments for "unstable" hold up well enough to make the simpler term the better choice: * no question around using a hyphen or not * "unstable public C API" is sufficient to distinguish the new tier from Py_BUILD_CORE's completely unstable internal API The risks of misinterpretation are also low: * external users that need one of these APIs will presumably be invested enough to actually check the stability expectations in the docs * core devs will have regression tests to remind us that the published unstable APIs aren't allowed to change after beta 1 Cheers, Nick. > -- > --Guido van Rossum (python.org/~guido) > *Pronouns: he/him **(why is my pronoun here?)* > <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/> >
_______________________________________________ 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/6TVQ6MEVKNLYNQAHMQHCHDMJES7RIRXL/ Code of Conduct: http://python.org/psf/codeofconduct/
