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 | amaury.forgeotdarc |
|---|---|
| Recipients | amaury.forgeotdarc, benjamin.peterson, georg.brandl, gvanrossum, jmillikin, lemburg |
| Date | 2008年04月08日.23:55:37 |
| SpamBayes Score | 0.1041317 |
| Marked as misclassified | No |
| Message-id | <1207698939.28.0.266221704026.issue2541@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I mean: now that raw strings cannot represent all unicode points (or more precisely, they need the file encoding to do so), is there a use case for "raw-unicode-escape" that cannot be filled by the unicode-escape codec? Note that pickle does not use "raw-unicode-escape" as is: it replaces backslashes by \u005c. This has the nice effect that pickled strings can also be decoded by "unicode-escape". That's why I propose to completely remove raw-unicode-escape, and use unicode-escape instead. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月08日 23:55:39 | amaury.forgeotdarc | set | spambayes_score: 0.104132 -> 0.1041317 recipients: + amaury.forgeotdarc, lemburg, gvanrossum, georg.brandl, benjamin.peterson, jmillikin |
| 2008年04月08日 23:55:39 | amaury.forgeotdarc | set | spambayes_score: 0.104132 -> 0.104132 messageid: <1207698939.28.0.266221704026.issue2541@psf.upfronthosting.co.za> |
| 2008年04月08日 23:55:38 | amaury.forgeotdarc | link | issue2541 messages |
| 2008年04月08日 23:55:38 | amaury.forgeotdarc | create | |