[Python-Dev] RFC: PEP 460: Add bytes % args and bytes.format(args) to Python 3.5
Eric V. Smith
eric at trueblade.com
Mon Jan 6 15:54:09 CET 2014
More information about the Python-Dev mailing list
Mon Jan 6 15:54:09 CET 2014
- Previous message: [Python-Dev] RFC: PEP 460: Add bytes % args and bytes.format(args) to Python 3.5
- Next message: [Python-Dev] RFC: PEP 460: Add bytes % args and bytes.format(args) to Python 3.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 01/06/2014 09:50 AM, Xavier Morel wrote: > On 2014-01-06, at 14:44 , Antoine Pitrou <solipsis at pitrou.net> wrote: >>> Then, >>> the following points must be decided to define the complete list of >>> supported features (formatters): >>> >>> * Format integer to hexadecimal? ``%x`` and ``%X`` >>> * Format integer to octal? ``%o`` >>> * Format integer to binary? ``{!b}`` >>> * Alignment? >>> * Truncating? Truncate or raise an error? >> >> Not desirable IMHO. bytes formatting should serve mainly for templating >> situations (i.e. catenate and insert bytestrings into one another). We >> cannot start giving text-like semantics to bytes objects without >> confusing non-experts. > > But having at least some of struct's formatting options available on > bytes.format or bytes % would be useful. Perhaps, but the PEP's stated goal is to make porting between 2.x and 3.5 easier. Add struct formatting to 3.5 wouldn't help. Eric.
- Previous message: [Python-Dev] RFC: PEP 460: Add bytes % args and bytes.format(args) to Python 3.5
- Next message: [Python-Dev] RFC: PEP 460: Add bytes % args and bytes.format(args) to Python 3.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list