<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/12/2014 6:11 PM, Guido van Rossum
wrote:<br>
</div>
<blockquote
cite="mid:CAP7+vJJ_L1QyYfSHMsQ6_VE3GHrsxUaGvdbuVfWCbb3UXTT5Zw@mail.gmail.com"
type="cite">
<pre wrap="">On Sun, Jan 12, 2014 at 5:27 PM, Ethan Furman <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:ethan@stoneleaf.us"><ethan@stoneleaf.us></a> wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>On 01/12/2014 04:47 PM, Guido van Rossum wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">>> </span>%s seems the trickiest: I think with a bytes argument it should just
<span class="moz-txt-citetags">>> </span>insert those bytes (and the padding modifiers should work too), and
<span class="moz-txt-citetags">>> </span>for other types it should probably work like %a, so that it works as
<span class="moz-txt-citetags">>> </span>expected for numeric values, and with a string argument it will return
<span class="moz-txt-citetags">>> </span>the ascii()-variant of its repr(). Examples:
<span class="moz-txt-citetags">>></span>
<span class="moz-txt-citetags">>> </span>b'%s' % 42 == b'42'
<span class="moz-txt-citetags">>> </span>b'%s' % 'x' == b"'x'" (i.e. the three-byte string containing an 'x'
<span class="moz-txt-citetags">>> </span>enclosed in single quotes)
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>I'm not sure about the quotes. Would anyone ever actually want those in the
<span class="moz-txt-citetags">> </span>byte stream?
</pre>
</blockquote>
<pre wrap="">Perhaps not, but it's a hint that you should probably think about an
encoding. It's symmetric with how '%s' % b'x' returns "b'x'". Think of
it as payback time. <span class="moz-smiley-s1" title=":-)"><span>:-)</span></span></pre>
</blockquote>
<br>
+1<br>
<br>
Quotes in the stream are a great debug hint, without blowing up.<br>
<br>
+1 to the whole reboot solution, also. It cures the problems people
are having, and there is no ambiguity.<br>
<br>
So then the question is whether to proceed with 3.4, delay this
feature to 3.5, or to delay 3.4 to include this feature, both have
been discussed, with the justification for the latter being to make
3.4 the ultimate Python 3 porting target for recalcitrant module
authors, sooner than later.<br>
</body>
</html>