Message311816
The behaviour here is intentional, though the reasons for doing it this way are at least partly historical: it's the way that %g formatting works in C's *printf functions (see C99 7.19.6.1p8 for details), and as a direct result of that it's also the way that old-style %-based formatting works in Python. That behaviour then got transferred to the new-style .format-based formatting for consistency.
I don't think we can or should change the current behaviour here: there's a significant risk of breaking existing code.
However, note that C does offer an *alternate* mode for .g-style formatting, using the '#' character, and this is also available in Python's formatting, both %-based and format-based:
>>> "%.2g" % 0.1950
'0.2'
>>> "%#.2g" % 0.1950
'0.20'
and
>>> format(0.1950, '.2g')
'0.2'
>>> format(0.1950, '#.2g')
'0.20'
Does this meet your needs? |
|
Date |
User |
Action |
Args |
2018-02-08 08:14:27 | mark.dickinson | set | recipients:
+ mark.dickinson, eric.smith, sk1d |
2018-02-08 08:14:27 | mark.dickinson | set | messageid: <1518077667.03.0.467229070634.issue32790@psf.upfronthosting.co.za> |
2018-02-08 08:14:27 | mark.dickinson | link | issue32790 messages |
2018-02-08 08:14:26 | mark.dickinson | create | |
|