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 bob.ippolito
Recipients benjamin.peterson, bob.ippolito, brett.cannon, christian.heimes, georg.brandl, pjenvey
Date 2008-05-06.14:52:21
SpamBayes Score 0.00617673
Marked as misclassified No
Message-id <1210085543.77.0.263029907178.issue2750@psf.upfronthosting.co.za>
In-reply-to
Content
loads will take unicode or str. if it's str then it assumes utf-8,
otherwise the explicitly specified encoding. All of the string instances
generated by loads will be unicode objects (some of them may be str
objects if they're all ASCII as an optimization, I'm not sure if I
implemented that or not).

dumps produces an ASCII str, but if you explicitly specify
ensure_ascii=False then it will return a unicode object.

obviously load and dump will be working on a file-like object so should
be dealing with bytes...

I'm not entirely sure whether semantically dumps should produce bytes or
str in py3k, I guess whatever the other text-based encodings do is
appropriate (e.g. base64, mime).
History
Date User Action Args
2008-05-06 14:52:24bob.ippolitosetspambayes_score: 0.00617673 -> 0.00617673
recipients: + bob.ippolito, brett.cannon, georg.brandl, christian.heimes, pjenvey, benjamin.peterson
2008-05-06 14:52:24bob.ippolitosetspambayes_score: 0.00617673 -> 0.00617673
messageid: <1210085543.77.0.263029907178.issue2750@psf.upfronthosting.co.za>
2008-05-06 14:52:23bob.ippolitolinkissue2750 messages
2008-05-06 14:52:22bob.ippolitocreate