Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Ian Kelly <ian.g.kelly@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: Curious Omission In New-Style Formats
Date: Sun, 10 Jul 2016 01:21:40 -0600
Lines: 33
Message-ID: <mailman.161.1468135349.2295.python-list@python.org>
References: <834b1cce-38dd-474c-8915-4ff1cd6b27ec@googlegroups.com> <CALwzidmwcc0nTLtLBJm=JNAjOQNRe2umtmNXNAk=s+xoyxhU6Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <834b1cce-38dd-474c-8915-4ff1cd6b27ec@googlegroups.com>
Precedence: list
Xref: csiph.com comp.lang.python:111237

On Sat, Jul 9, 2016 at 11:54 PM, Lawrence D=E2=80=99Oliveiro
<lawrencedo99@gmail.com> wrote:
> In printf-style formats, you can specify the number of digits for an inte=
ger separately from the field width. E.g.
>
>     >>> "%#0.5x" % 0x123
>     '0x00123'
>
> but not in new-style formats:
>
>     >>> "{:#0.5x}".format(0x123)
>     Traceback (most recent call last):
>       File "<stdin>", line 1, in <module>
>     ValueError: Precision not allowed in integer format specifier
>
> The field width itself doesn=E2=80=99t give the right number of digits in=
 this case:
>
>     >>> "{:#05x}".format(0x123)
>     '0x123'
>
> because you lose 2 characters for the =E2=80=9C0x=E2=80=9D prefix.

So add 2 to the field width to account for the fixed-size prefix.

>>> '{:#07x}'.format(0x123)
'0x00123'

It's specified in PEP 3101 that the precision is ignored for integer
conversions. Apparently that changed from "ignored" to "not allowed"
in 3.1, as per the documentation. I'm not sure what the reasoning was,
except perhaps that precision doesn't really make sense for integers
in the first place.