Message 80330 - Python tracker

➜

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	bronger
Recipients	alexandre.vassalotti, bronger, dddibagh, georg.brandl, lemburg, loewis, mawbid
Date	2009-01-21.15:43:28
SpamBayes Score	1.0447634e-07
Marked as misclassified	No
Message-id	<1232552609.49.0.655275641566.issue2980@psf.upfronthosting.co.za>
In-reply-to

Content
I ran into this problem today when writing python data structures into a database. Only ASCII is safe in this situation. I understood the Python docs that protocol 0 was ASCII-only. I use pickle+base64 now, however, this makes debugging more difficult. Anyway, I think that the docs should clearly say that protocol 8 is not ASCII-only because this is important in the Python world. For example, I saw this issue because Django makes an implicit unicode() conversion with my input which fails with non-ASCII.

I ran into this problem today when writing python data structures into a
database.  Only ASCII is safe in this situation.  I understood the
Python docs that protocol 0 was ASCII-only.

I use pickle+base64 now, however, this makes debugging more difficult.

Anyway, I think that the docs should clearly say that protocol 8 is not
ASCII-only because this is important in the Python world.  For example,
I saw this issue because Django makes an implicit unicode() conversion
with my input which fails with non-ASCII.

History
Date	User	Action	Args
2009-01-21 15:43:29	bronger	set	recipients: + bronger, lemburg, loewis, georg.brandl, alexandre.vassalotti, mawbid, dddibagh
2009-01-21 15:43:29	bronger	set	messageid: <1232552609.49.0.655275641566.issue2980@psf.upfronthosting.co.za>
2009-01-21 15:43:28	bronger	link	issue2980 messages
2009-01-21 15:43:28	bronger	create