Message 129762 - 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	asdfasdfasdfasdfasdfasdfasdf
Recipients	alex, asdfasdfasdfasdfasdfasdfasdf
Date	2011-03-01.13:33:17
SpamBayes Score	1.1289425e-05
Marked as misclassified	No
Message-id	<AANLkTimfVfXey8aZcXaZHr8dEDfZOqdSO7+d4N-qnHJS@mail.gmail.com>
In-reply-to	<1298962903.1.0.997948298584.issue11358@psf.upfronthosting.co.za>

Content
On 1 March 2011 18:01, Alex <report@bugs.python.org> wrote: > > Alex <alex.gaynor@gmail.com> added the comment: > > Why? JSON is incapable of representing most Python datastructures that can be pickled (i.e. anything that isn't a list, tuple, dict, int, or str). I would have suggested yaml (using safe_load() ) . However there isn't a 'core' yaml module afaik. If you wanted to actually transfer a complex python data-structure no one would stop you from pickling it and sending it (json'ed).

On 1 March 2011 18:01, Alex <report@bugs.python.org> wrote:
>
> Alex <alex.gaynor@gmail.com> added the comment:
>
> Why?  JSON is incapable of representing most Python datastructures that can be pickled (i.e. anything that isn't a list, tuple, dict, int, or str).

I would have suggested yaml (using safe_load() ) . However there isn't
a 'core' yaml module afaik.

If you wanted to actually transfer a complex python data-structure no
one would stop you from pickling it and sending it (json'ed).

History
Date	User	Action	Args
2011-03-01 13:33:18	asdfasdfasdfasdfasdfasdfasdf	set	recipients: + asdfasdfasdfasdfasdfasdfasdf, alex
2011-03-01 13:33:18	asdfasdfasdfasdfasdfasdfasdf	link	issue11358 messages
2011-03-01 13:33:17	asdfasdfasdfasdfasdfasdfasdf	create