Ethan Furman ethan at stoneleaf.us
Sun Mar 15 07:58:23 CET 2015

• Previous message (by thread): [Python-Dev] backwards and forwards compatibility, the exact contents of pickle files, and IntEnum
• Next message (by thread): [Python-Dev] backwards and forwards compatibility, the exact contents of pickle files, and IntEnum
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On 03/14/2015 11:46 PM, Glenn Linderman wrote:

> In general, it would seem to me that each version of Python could add object types that are foreign to prior versions,
> and so as long as version N can unpickle anything produced by versions <=N, all would be well.

The question to me is because we not so much adding something brand-new (socket.AF_INET has been there for ages), as
changing the type of something already existing -- I'm just not sure if we need "end-result" compatibility (achieved by
the first option) or if we need "bug for bug" compatibility (achieved by the second option).

--
~Ethan~

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150314/b5187bec/attachment.sig>

---

• Previous message (by thread): [Python-Dev] backwards and forwards compatibility, the exact contents of pickle files, and IntEnum
• Next message (by thread): [Python-Dev] backwards and forwards compatibility, the exact contents of pickle files, and IntEnum
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list