On 8/13/2021 8:45 PM, Guido van Rossum wrote:
Now, backwards compatibility is still nothing to sneeze at, but at least we don't have to hem and haw about ABI compatibility.
If back compatibility were our sacred prime directive, then we would not (or should not) have changed code objects in way that threatens it.
The question then is, can we break (source) backwards compatibility for these two functions, because in practice code objects have been unstable?
I presume that the existence of those functions is based on an expectation of stability that may have been true for years, but not recently. Or an expectation that any change would be part of a one-time overhaul where compatibility was suspended as much as for 3.0. I think that whatever we do now should allow for continued version-by-version changes in the future.
-- Terry Jan Reedy _______________________________________________ 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/JKHISUP624VI7MVUG7XPYO5QTBLFIUT2/ Code of Conduct: http://python.org/psf/codeofconduct/
