I think it makes sense, and I do see a difference between Provisional and Unstable. Is this anything more than a documentation label?
-Barry > On Jun 3, 2021, at 13:10, Guido van Rossum <gu...@python.org> wrote: > > This is not a complete thought yet, but it occurred to me that while we have > deprecated APIs (which will eventually go away), and provisional APIs (which > must mature a little before they're declared stable), and stable APIs (which > everyone can rely on), it might be good to also have something like > *unstable* APIs, which will continually change without ever going away or > stabilizing. Examples would be the ast module (since the AST structure > changes every time the grammar changes) and anything to do with code objects > and bytecode (since we sometimes think of better ways to execute Python). > > So maybe the docs should grow a standard way of saying "this is an unstable > API"? > > Would we need a PEP to create an initial list of APIs (modules, classes, > etc.) that are considered unstable? > > -- > --Guido van Rossum (python.org/~guido) > Pronouns: he/him (why is my pronoun here?) > _______________________________________________ > 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/JM6SQ2YNMDAKXYD5O54QWMVR2X7QOXVL/ > Code of Conduct: http://python.org/psf/codeofconduct/
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ 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/IKNRQSWBZMKQRACSZY6OOCSMJVZHFIY3/ Code of Conduct: http://python.org/psf/codeofconduct/
