Mark Dickinson <dicki...@gmail.com> added the comment: 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 188.8.131.52p8 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? ---------- nosy: +eric.smith, mark.dickinson _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32790> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com