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 joelpitt
Recipients alexandre.vassalotti, bronger, dddibagh, georg.brandl, joelpitt, lemburg, loewis, mawbid, pitrou, terry.reedy, wdoekes
Date 2012-12-12.04:55:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355288111.91.0.901998605539.issue2980@psf.upfronthosting.co.za>
In-reply-to
Content
Just ran into this problem using Python 2.7.3 and the issue others mention in conjunction with Django.

Note the 2.7 docs still imply it's ASCII: http://docs.python.org/2/library/pickle.html#data-stream-format

It has a weak caveat "(and of some other characteristics of pickle‘s representation)", but if you only skim read the bullet points below you'll miss that.

Yes I will use base64 to get around this, but the point is the documentation is still unclear and should probably completely remove the reference to ASCII in favour of "human-readable"... or even better, explicitly mention what will happen with unicode.
History
Date User Action Args
2012-12-12 04:55:12joelpittsetrecipients: + joelpitt, lemburg, loewis, georg.brandl, terry.reedy, pitrou, bronger, alexandre.vassalotti, mawbid, dddibagh, wdoekes
2012-12-12 04:55:11joelpittsetmessageid: <1355288111.91.0.901998605539.issue2980@psf.upfronthosting.co.za>
2012-12-12 04:55:11joelpittlinkissue2980 messages
2012-12-12 04:55:11joelpittcreate