Peter Wang pwang at anaconda.com
Fri Apr 26 17:57:31 EDT 2019

• Previous message (by thread): [Python-Dev] Increasing the C-optimized pickle extensibility
• Next message (by thread): [Python-Dev] Steering Council Update for April 2019
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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 <guido at 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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190426/970d3785/attachment.html>

---

• Previous message (by thread): [Python-Dev] Increasing the C-optimized pickle extensibility
• Next message (by thread): [Python-Dev] Steering Council Update for April 2019
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list