This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.smith
Recipients BreamoreBoy, aubmoon, eric.smith, mark.dickinson, ned.deily, skrah
Date 2014-03-01.23:17:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1393715820.5.0.370772685893.issue20811@psf.upfronthosting.co.za>
In-reply-to
Content
I still think this is a special case that we won't "fix". And even if we did, you'd have to wait until 3.5.

But instead of your solution, it might be easier to wrap your floats in a class that implements your version of format, based on float's format with some post-processing:

class MyFloat(float):
    def __format__(self, fmt):
        s = float.__format__(self, fmt)
        if s[1] == '0':
            return s[0] + s[2:]
        return s

print(format(MyFloat(0.12345678), '+8.8'))
print(format(MyFloat(1.12345678), '+8.8'))

gives:
+.12345678
+1.1234568

I've grossly simplified __format__, of course. And I'm using built-in format() instead of ''.format() (because it's less typing), but they use the same mechanisms. So:

print('{}:"{:+10.8}"'.format('answer', MyFloat(0.12345678)))

gives:
answer:"+.12345678"
History
Date User Action Args
2014-03-01 23:17:00eric.smithsetrecipients: + eric.smith, mark.dickinson, ned.deily, skrah, BreamoreBoy, aubmoon
2014-03-01 23:17:00eric.smithsetmessageid: <1393715820.5.0.370772685893.issue20811@psf.upfronthosting.co.za>
2014-03-01 23:17:00eric.smithlinkissue20811 messages
2014-03-01 23:17:00eric.smithcreate