Message93516
| Author |
Rhamphoryncus |
| Recipients |
Rhamphoryncus, benjamin.peterson, ezio.melotti, hippietrail, jwilk, l.mastrodomenico, lemburg, terry.reedy |
| Date |
2009年10月04日.00:09:25 |
| SpamBayes Score |
4.1831498e-07 |
| Marked as misclassified |
No |
| Message-id |
<1254614968.56.0.957346980958.issue3297@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Looks like the failure mode has changed here, presumably due to issue
#3672 patches. It now always fails, even after loading from a .pyc.
This is using py3k via bzr, which reports itself as 3.2a0
$ rm unicodetest.pyc
$ ./python -c 'import unicodetest'
Result: False
Len: 2 1
Repr: '\ud800\udd23' '\U00010123'
[28877 refs]
$ ./python -c 'import unicodetest'
Result: False
Len: 2 1
Repr: '\ud800\udd23' '\U00010123'
[28708 refs] |
|