I'm curious why the addition of a new feature, past beta 1, was constrained entirely to a single tracker issue. Clearly not enough people were aware of it (or there wouldn't be the discussion about it here).
Following the discussion in the issue tracker is really hard (since most of the discussion apparently refers to earlier versions). I also don't see any doc changes. If you want to keep the feature, at least write some documentation for it so everyone knows what is actually implemented, and why, without having to go to the source. --Guido On Tue, Jun 24, 2008 at 11:44 AM, Raymond Hettinger <[EMAIL PROTECTED]> wrote: >>>>>> bin(1.0) >>> >>> '0b1 * 2.0 ** 0' >>>>>> >> >> Oops. > > This was checked-in for Issue 3008 which has been under discussion and > development for a while. It was intentionally held until after the beta was > released so that the beta itself would be as stable as possible (in the > final week and a half most of the bots were red and it made no sense to > commit a feature request at that time). > > The patch allows a eval-able representation of a float that works across > platforms and is not dependent of %.17g, atof() or ftoa() routines. The > tool makes it much easier to examine or explain what floating point ops > really do. It was invaluable in the development of math.sum(). I've spent > several days of development time on this and would be really bummed if it > got reversed-out at this point. > > The use of __bin__ is not essential to its implementation so that > implementation detail can be changed if needed. > > > Raymond > > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ 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
