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月08日.20:03:23 |
| SpamBayes Score | 0.04400678 |
| Marked as misclassified | No |
| Message-id | <1207685008.93.0.089955394818.issue2541@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
You can't change the codec - it's being used in other places as well, e.g. for use cases where you need to have an 8-bit encoded readable version of a Unicode object (which happens to be Latin-1 + Unicode escapes for all non-Latin-1 characters, due to Unicode being a superset of Latin-1). Adding a new codec would be fine, though I don't know how this would map raw Unicode strings with non-Latin-1 characters in them to an 8-bit string. Perhaps this is not needed at all in Py3k. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月08日 20:03:30 | lemburg | set | spambayes_score: 0.0440068 -> 0.04400678 recipients: + lemburg, gvanrossum, georg.brandl, amaury.forgeotdarc, benjamin.peterson, jmillikin |
| 2008年04月08日 20:03:29 | lemburg | set | spambayes_score: 0.0440068 -> 0.0440068 messageid: <1207685008.93.0.089955394818.issue2541@psf.upfronthosting.co.za> |
| 2008年04月08日 20:03:27 | lemburg | link | issue2541 messages |
| 2008年04月08日 20:03:25 | lemburg | create | |