Message247009
| Author |
r.david.murray |
| Recipients |
ezio.melotti, fgallaire, georg.brandl, pitrou, r.david.murray, serhiy.storchaka, vstinner |
| Date |
2015年07月21日.01:13:26 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1437441208.44.0.704886085247.issue24665@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The problem is (if I'm understanding this correctly, which I may not be, I'm not a unicode expert) is that how you compute and manipulate CJK characters in python2 differs depending on whether you are dealing with a wide build or a narrow build. And the fact that python3 doesn't handle it either is why this would be a new feature (see the referenced issues).
But I could be wrong. I leave it to the unicode experts. |
|