diff options
author | Thomas Cellerier <thomascellerier@gmail.com> | 2022-05-03 12:12:58 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-05-03 12:12:58 (GMT) |
commit | 52dc9c3066bcdc67a7a45d41cf158ecb1434d5f3 (patch) | |
tree | 87388bf8306586e9ada724873ec5911e97352cf5 /Python/dynload_hpux.c | |
parent | ec8d3adb99f1ad93786fed5c1def5119b6ec73c0 (diff) | |
download | cpython-52dc9c3066bcdc67a7a45d41cf158ecb1434d5f3.zip cpython-52dc9c3066bcdc67a7a45d41cf158ecb1434d5f3.tar.gz cpython-52dc9c3066bcdc67a7a45d41cf158ecb1434d5f3.tar.bz2 |
bpo-46415: Use f-string for ValueError in ipaddress.ip_{address,network,interface} helper functions (#30642)
`IPv*Network` and `IPv*Interface` constructors accept a 2-tuple of
(address description, netmask) as the address parameter.
When the tuple-based address is used errors are not propagated
correctly through the `ipaddress.ip_*` helper because of the %-formatting now expecting several arguments:
In [7]: ipaddress.ip_network(("192.168.100.0", "fooo"))
...
TypeError: not all arguments converted during string formatting
Compared to:
In [8]: ipaddress.IPv4Network(("192.168.100.0", "foo"))
...
NetmaskValueError: 'foo' is not a valid netmask
Use an f-string to make sure the error is always properly formatted.
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Diffstat (limited to 'Python/dynload_hpux.c')
0 files changed, 0 insertions, 0 deletions