RetroSearch Browse

Tue Sep 30 22:22:07 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-September/082691.html

> I didn't get an answer to my question: what is the result <bytes (fake 
> characters) stored in unicode> + <real unicode>? I guess that the result is 
> <mixed "bytes" and characters in unicode> instead of raising an error 
> (invalid types). So again: why introducing a new type instead of reusing 
> existing Python types?

I didn't mean to introduce a new data type in the strict sense - merely
to pass through undecodable bytes through the regular Unicode type.
So the result of adding them is a regular Unicode string.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-September/082691.html below:

[Python-Dev] [Python-3000] New proposition for Python3 bytes filename issue