This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aggieNick02
Recipients aggieNick02, josh.r, serhiy.storchaka
Date 2019-09-23.13:29:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1569245368.74.0.155711207509.issue38241@roundup.psfhosted.org>
In-reply-to
Content
Apologies as I'm not super-familiar with Latin1 or how Python refers to Latin1, but it seems a little odd to even call it Latin1. It can be decoded as Latin1, but it can contain every possible byte, including 0x7f through 0x9f, which aren't really Latin1. It is human readable when pickling certain data types, but when others are involved, it sure seems like binary to me.

I think that is fine, and perhaps all that needs to be done is to update the documentation to say something like: "Protocol level 0 is the original pickling format. It is the default for Python 2 and is now a binary format; it originally was an ASCII format but this ceased to be true as support for new datatypes was added to Python."
History
Date User Action Args
2019-09-23 13:29:28aggieNick02setrecipients: + aggieNick02, serhiy.storchaka, josh.r
2019-09-23 13:29:28aggieNick02setmessageid: <1569245368.74.0.155711207509.issue38241@roundup.psfhosted.org>
2019-09-23 13:29:28aggieNick02linkissue38241 messages
2019-09-23 13:29:28aggieNick02create