RetroSearch Browse

Mon Feb 24 18:58:30 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-February/132740.html

On 02/24/2014 09:43 AM, Antoine Pitrou wrote:
> On Mon, 24 Feb 2014 09:15:29 -0800
> Ethan Furman <ethan at stoneleaf.us> wrote:
>> On 02/23/2014 02:54 PM, Nick Coghlan wrote:
>>>
>>> It's a harm containment tactic, based on the assumption people *will*
>>> want to include the output of ascii() in binary protocols containing
>>>   ASCII segments, regardless of whether or not we consider their reasons
>>> for doing so to be particularly good.
>>
>> One possible problem with %a -- it becomes the bytes equivalent of %s in Python 2 strings, with the minor exception of
>> how unicode strings are handled (quote marks are added).  In other words, instead of %d, one could use %a.
>>
>> On the other hand, %a is so much more user-friendly than b'%s' % ('%d' % 123).encode('ascii', errors='backslashreplace').
>
> But why not b'%d' % 123 ?

I was just using 123 as an example of the user-unfriendliness of the rest of that line.

--
~Ethan~

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

Showing content from https://mail.python.org/pipermail/python-dev/2014-February/132740.html below:

[Python-Dev] PEP 461: Adding % formatting to bytes and bytearray -- Final, Take 2