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 belopolsky
Recipients belopolsky, pitrou, rhettinger
Date 2008-05-30.13:55:16
SpamBayes Score 0.13393769
Marked as misclassified No
Message-id <1212155724.85.0.878421784499.issue3008@psf.upfronthosting.co.za>
In-reply-to
Content
I like the idea in general.  It is way too common for people to be 
confused by decimal representation of floats, so an obvious mechanism to 
display the true value will be helpful.

I don't think a promiscuous bin() will lead to obscure bugs. Antoine 
will  have to give a specific example to convince me otherwise.  I can 
see, that extending :b format to floats may be a problem, but this is 
not being proposed.

As far as the proposed implementation goes, I don't like the fact that 
it always returns a fixed rather than floating point notation. (Try 
vis(1e100)).  I think it should behave somewhat like "%g" format.

If bin() is extended to floats, it may become confusing that hex() and 
oct() are not similarly extended.
History
Date User Action Args
2008-05-30 13:55:25belopolskysetspambayes_score: 0.133938 -> 0.13393769
recipients: + belopolsky, rhettinger, pitrou
2008-05-30 13:55:25belopolskysetspambayes_score: 0.133938 -> 0.133938
messageid: <1212155724.85.0.878421784499.issue3008@psf.upfronthosting.co.za>
2008-05-30 13:55:23belopolskylinkissue3008 messages
2008-05-30 13:55:22belopolskycreate