[Python-Dev] email package status in 3.X (original) (raw)
Steven D'Aprano steve at pearwood.info
Tue Jun 22 01:23:28 CEST 2010
- Previous message: [Python-Dev] email package status in 3.X
- Next message: [Python-Dev] email package status in 3.X
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 22 Jun 2010 06:09:52 am P.J. Eby wrote:
However, if you promoted mixed-type operation results to unicode instead of ebytes, then you:
1) can't preserve data that doesn't have a 1:1 mapping to unicode,
Sounds like exactly the sort of thing the Unicode private codepoints were invented for, as Toshio suggests.
In any case, if there are use-cases for text that aren't solved by Unicode, and I'm not convinced that there are, Python doesn't need to solve them. At the very least, such a solution should start off as a third-party package to prove itself before being made a part of the standard library, let alone a built-in.
-- Steven D'Aprano
- Previous message: [Python-Dev] email package status in 3.X
- Next message: [Python-Dev] email package status in 3.X
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]