Mark Dickinson <dicki...@gmail.com> added the comment: Thanks, Eric. All those changes look good to me.
Out of interest, what does '%#.0f' % 1.5 produce on Python 2.7/Windows? I'd expect to get '2.' both for round-half-to-even and round-half-away-from-zero. Does Windows round this down to '1.' instead? I'm surprised by the %#.ng results for 0; this looks like questionable behaviour (producing n+1 digits when only n significant digits were requested). Is the MS implementation of printf directly responsible for this, or is the CPython code somehow adding the extra 0? If this is just the way that Windows behaves for formatting of zeros, then I suppose we could add code to work around this, but it's not clear that it's really worth it. I suspect that we're in for some complaints when Windows users discover that Python 3.1 string formatting does round-half-to-even rather than the round-half-up they're used to in Python 2.x. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6198> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
