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 | amaury.forgeotdarc, benjamin.peterson, georg.brandl, gvanrossum, jmillikin, lemburg |
| Date | 2008年04月09日.10:03:23 |
| SpamBayes Score | 0.39483947 |
| Marked as misclassified | No |
| Message-id | <1207735405.83.0.415384587848.issue2541@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
While that's true for cPickle, it is not for pickle. The pickle protocol itself is defined in terms of the "raw-unicode-escape" codec (see pickle.py). Besides, you cannot assume that the Python interpreter itself is the only use-case for these codecs. The "raw-unicode-escape" codec is well usable for other purposes where you need a compact way of encoding Unicode, especially if you're strings are mostly Latin-1 and only include non-UCS2 code points every now and then. That's also the reason why pickle uses it. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月09日 10:03:26 | lemburg | set | spambayes_score: 0.394839 -> 0.39483947 recipients: + lemburg, gvanrossum, georg.brandl, amaury.forgeotdarc, benjamin.peterson, jmillikin |
| 2008年04月09日 10:03:25 | lemburg | set | spambayes_score: 0.394839 -> 0.394839 messageid: <1207735405.83.0.415384587848.issue2541@psf.upfronthosting.co.za> |
| 2008年04月09日 10:03:25 | lemburg | link | issue2541 messages |
| 2008年04月09日 10:03:24 | lemburg | create | |