<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#330033">
<div class="moz-cite-prefix">On 1/13/2014 9:38 AM, Ethan Furman
wrote:<br>
</div>
<blockquote cite="mid:52D42499.1070001@stoneleaf.us" type="cite">On
01/13/2014 09:31 AM, Antoine Pitrou wrote:
<br>
<blockquote type="cite" style="color: #000000;">On Mon, 13 Jan
2014 08:36:05 -0800
<br>
Ethan Furman wrote:
<br>
<blockquote type="cite" style="color: #000000;">
<br>
You mean crash all the time? I'd be fine with that for both
the str case
<br>
and the bytes case. But's probably too late
<br>
to change the str case, and the bytes case should mirror what
str does.
<br>
</blockquote>
<br>
Let me add something else: str and bytes don't have to be
symmetrical.
<br>
In Python 2, str and unicode were symmetrical, they allowed
exactly the
<br>
same operations and were composable.
<br>
In Python 3, str and bytes are different beasts; they have
different
<br>
operations <b class="moz-txt-star"><span class="moz-txt-tag">*</span>and<span
class="moz-txt-tag">*</span></b> different semantics (for
example, bytes interoperates
<br>
with bytearray and memoryview, while str doesn't).
<br>
</blockquote>
<br>
This makes sense to me.
<br>
<br>
So I'm guess I'm fine with either the quoted ascii repr or the
always blowing up method, with leaning towards the blowing up
method.
</blockquote>
<br>
+1 - what Ethan said. A real death, instead death by inappropriately
transformed data, is fine by me, if b"%s" % str(...) doesn't have
the appropriate .encode(...) call. But I could live with either.<br>
</body>
</html>