Message 80337 - 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.18:34:44
SpamBayes Score	5.940701e-08
Marked as misclassified	No
Message-id	<1232562885.54.0.993704268462.issue2980@psf.upfronthosting.co.za>
In-reply-to

Content
Well, Django doesn't story binary data at all but wants you to store image files etc in the file system. Whether this was a good design decision, is beyond the scope of this issue. My points actually are only these: a) the docs strongly suggest that protocol 0 is ASCII-only and this should be clarified (one sentence would be fully sufficient I think) b) currently, there is no way in the standard lib to serialise data in a debuggable, ASCII-only format Probably b) is not important. I want to have it currently but this doesn't mean much.

Well, Django doesn't story binary data at all but wants you to store
image files etc in the file system.  Whether this was a good design
decision, is beyond the scope of this issue.  My points actually are
only these:

a) the docs strongly suggest that protocol 0 is ASCII-only and this
should be clarified (one sentence would be fully sufficient I think)

b) currently, there is no way in the standard lib to serialise data in a
debuggable, ASCII-only format

Probably b) is not important.  *I* want to have it currently but this
doesn't mean much.

History
Date	User	Action	Args
2009-01-21 18:34:45	bronger	set	recipients: + bronger, lemburg, loewis, georg.brandl, alexandre.vassalotti, mawbid, dddibagh
2009-01-21 18:34:45	bronger	set	messageid: <1232562885.54.0.993704268462.issue2980@psf.upfronthosting.co.za>
2009-01-21 18:34:44	bronger	link	issue2980 messages
2009-01-21 18:34:44	bronger	create