<div class="gmail_quote">On Tue, Jun 24, 2008 at 8:05 PM, Guido van Rossum <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Following the discussion in the issue tracker is really hard (since<br>
most of the discussion apparently refers to earlier versions). I also<br>
don't see any doc changes.</blockquote><div><br></div><div>I think there may also still be room for some additional discussion</div><div>on the output format; while being eval-able is nice, one not-so-nice</div><div>
aspect of the representation is that nearby floats can have</div><div>entirely distinct-looking representations; as in, for example:</div><div><br></div><div>>>> hex(126.38)</div><div>'0x3f30a3d70a3d7 * 2.0 ** -43'</div>
<div>>>> hex(126.39)<br></div><div>'0x1f98f5c28f5c29 * 2.0 ** -46'</div><div><br></div><div>bin() suffers much less from this, but on balance I think I'd</div><div>still prefer to see a non eval-able output that's normalized with</div>
<div>respect to the most-significant bit instead of the least.</div><div><br></div><div>I realize that (a) this has little to do with implementation</div><div>details and use or not of __bin__, and (b) I should have</div>
<div>said this in the issue tracker a few days ago.</div><div><br></div><div>Mark</div><div></div></div>