I strongly second not breaking backwards compatibility and interoperability, especially for persistent artifacts, unless there is a *REALLY* good reason. A potential unintended side effect of such breakages is that it slows down adoption of the new version.
-Peter On Fri, Apr 26, 2019 at 10:27 AM Guido van Rossum <gu...@python.org> wrote: > I think it's better not to introduce a new opcode, for the reason you > stated -- you don't want your pickles to be unreadable by older Python > versions, if you can help it. > >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
