Am 03.06.21 um 20:11 schrieb Gregory P. Smith:
The ideal way to declare an API as unstable is to constantly change it
in a breaking manner. With every release and potentially even within
some patch releases when the point really needs to be made. Even when
you didn't have a reason to change anything. If you don't do that,
people are going to find it convenient, discover stability, assume it
exists, depend on it, and complain about breakage no matter what was
stated. https://www.hyrumslaw.com/ <https://www.hyrumslaw.com/>
There is certainly value in having some stability guarantees, even in
"unstable" APIs. For example, while it is expected that the ast module
breaks with each new minor Python version (3.7, 3.8 etc.), it's still
stable during each such version. This makes the ast module quite useful
for lots of applications that work on Python source code and that are
understood to need changes for each Python version anyway. Breaking the
compatibility just for the sake of it would be counterproductive.
- Sebastian
_______________________________________________
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/7BBKPPUD7BX6THFFBWZXCUK3TBIFNNQS/
Code of Conduct: http://python.org/psf/codeofconduct/