> 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 _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
