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 lemburg
Recipients georg.brandl, lemburg, mawbid
Date 2008-05-27.18:20:36
SpamBayes Score 0.0034875148
Marked as misclassified No
Message-id <1211912437.68.0.151339793162.issue2980@psf.upfronthosting.co.za>
In-reply-to
Content
Actually, I was wrong: protocol 0 is the default if you don't specify
the protocol.

This set the binary flag to false, which should result in ASCII-only data.

The Unicode save routine uses the raw-unicode-escape codec, but this
only escapes non-Latin-1 characters and allows non-ASCII Latin-1
character to pass through.

Not sure what to do about this: we can't change the protocol anymore and
all higher protocol levels are binary already.

Perhaps we just need to remove the ASCII note from the documentation
altogether and only leave the "human readbable form" comment ?!
History
Date User Action Args
2008-05-27 18:20:37lemburgsetspambayes_score: 0.00348751 -> 0.0034875148
recipients: + lemburg, georg.brandl, mawbid
2008-05-27 18:20:37lemburgsetspambayes_score: 0.00348751 -> 0.00348751
messageid: <1211912437.68.0.151339793162.issue2980@psf.upfronthosting.co.za>
2008-05-27 18:20:36lemburglinkissue2980 messages
2008-05-27 18:20:36lemburgcreate