Message93562
| Author |
Rhamphoryncus |
| Recipients |
Rhamphoryncus, amaury.forgeotdarc, bupjae, ezio.melotti, lemburg, vstinner |
| Date |
2009年10月04日.21:46:51 |
| SpamBayes Score |
3.7605227e-07 |
| Marked as misclassified |
No |
| Message-id |
<1254692819.07.0.257919015869.issue5127@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Surrogates aren't optional features of UTF-16, we really need to get
this fixed. That includes .isalpha().
We might keep the old public API for compatibility, but it should be
clearly marked as broken for non-BMP scalar values.
I don't see a problem with changing 2.x. The existing behaviour is
broken for non-BMP scalar values, so surely nobody can claim dependence
on it. |
|