On 30.08.2014 01:37, Greg Ewing wrote:
M.-A. Lemburg wrote:
we needed
a way to make sure that Python 3 also optionally supports working
with lone surrogates in such UTF-8 streams (nowadays called CESU-8:
http://en.wikipedia.org/wiki/CESU-8).
I don't think CESU-8 is the same thing.
On 29.08.2014 02:41, Stephen J. Turnbull wrote:
In the process of booking up for my other post in this thread, I
noticed the 'surrogatepass' handler.
Is there a real use case for the 'surrogatepass' error handler? It
seems like a horrible break in the abstraction. IMHO, if there's a
need,
On 29.08.2014 13:22, Isaac Morland wrote:
On Fri, 29 Aug 2014, M.-A. Lemburg wrote:
On 29.08.2014 02:41, Stephen J. Turnbull wrote:
Since Python allows working with lone surrogates in Unicode (they
are valid code points) and we're using UTF-8 for marshal, we needed
a way to make sure that
On Fri, 29 Aug 2014, M.-A. Lemburg wrote:
On 29.08.2014 02:41, Stephen J. Turnbull wrote:
Since Python allows working with lone surrogates in Unicode (they
are valid code points) and we're using UTF-8 for marshal, we needed
a way to make sure that Python 3 also optionally supports working
with
M.-A. Lemburg wrote:
we needed
a way to make sure that Python 3 also optionally supports working
with lone surrogates in such UTF-8 streams (nowadays called CESU-8:
http://en.wikipedia.org/wiki/CESU-8).
I don't think CESU-8 is the same thing. According to the wiki
page, CESU-8 *requires* all
In the process of booking up for my other post in this thread, I
noticed the 'surrogatepass' handler.
Is there a real use case for the 'surrogatepass' error handler? It
seems like a horrible break in the abstraction. IMHO, if there's a
need, the application should handle this. Python shouldn't
