Message264711
| Author | arigo |
|---|---|
| Recipients | arigo, ezio.melotti, vstinner |
| Date | 2016-05-03.10:29:22 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1462271362.88.0.721035930399.issue26917@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
See also https://bitbucket.org/pypy/pypy/issues/2289/incorrect-unicode-normalization . It seems that you reached the same conclusion than the OP in that issue: the problem would really be that normalizing "\uafb8\u11a7" should not drop the second character. Both Python and PyPy do that, but Python adds the "is_normalized()" check, so in some cases it returns the correct unmodified result. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-05-03 10:29:22 | arigo | set | recipients: + arigo, vstinner, ezio.melotti |
| 2016-05-03 10:29:22 | arigo | set | messageid: <1462271362.88.0.721035930399.issue26917@psf.upfronthosting.co.za> |
| 2016-05-03 10:29:22 | arigo | link | issue26917 messages |
| 2016-05-03 10:29:22 | arigo | create | |