Message102523
| Author |
vstinner |
| Recipients |
dangra, ezio.melotti, lemburg, sjmachin, vstinner |
| Date |
2010年04月07日.09:02:02 |
| SpamBayes Score |
1.1079479e-05 |
| Marked as misclassified |
No |
| Message-id |
<201004071101.56629.victor.stinner@haypocalc.com> |
| In-reply-to |
<4BBC4451.7030704@egenix.com> |
| Content |
> >> I also found out that, according to RFC 3629, surrogates
> >> are considered invalid and they can't be encoded/decoded,
> >> but the UTF-8 codec actually does it.
> >
> > Python2 does, but Python3 raises an error.
> > (...)
>
> I wonder how that change got into the 3.x branch - I would certainly
> not have approved it for the reasons given further up on this ticket.
>
> I think we should revert that change for Python 3.2.
See r72208 and issue #3672.
pitrou wrote "We could fix it for 3.1, and perhaps leave 2.7 unchanged if some
people rely on this (for whatever reason)." |
|