Raymond Hettinger wrote:
and I'm definitely not keen on the fact that it's overloaded on the
hex/bin/oct builtins.
Can't it be a separate function?
Simplicity. bin/oct/hex have the job of giving alternate base
representations for numbers.
Nothing is gained by adding a duplicate set of functions in the math
module for float inputs.
I'd place additional requirements on using bin/oct/hex for this:
1. The new feature must be available to floating point types other than
float (such as Decimal) in both 2.6 and 3.0 (keeping in mind that 3.0
does not support __bin__, __hex__, or __oct__ methods - it uses only
__index__ to implement bin(), hex() and oct()
2. Other classes (such as Decimal) should be able to leverage the
formatting functionality provided for floats.
If it was just a new method on float objects or a new function in the
math module, neither of those additional requirements would apply - I
would be completely fine with the function only working for actual float
objects.
However, in either case, I think this also runs afoul of the "we're in
beta" argument - yes, it's a nice feature, but I don't think it's one
that will cause any great dramas if users don't get their hands on it
until 2.7/3.1.
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
