I don't want the discussion in the issue. I want to have it right here. While I think it's fine to have some function that reveals the binary representation of floats, I don't think that overlaying this on hex/oct/bin is worth the problems it causes. This API appears to be purely for educational purposes; why not implement something in pure Python using the struct module that reveals the lay-out of the floating-point value? (There are also several things wrong with the specific patch, apart from its lack of docs; #1 is the introduction of an externaly visible symbol that doesn't start with _Py.) --Guido On Tue, Jun 24, 2008 at 8:20 PM, Raymond Hettinger <python at rcn.com> wrote: > Issue 3008 has been re-opened for more commentary. > > Raymond > > ----- Original Message ----- From: "Guido van Rossum" <guido at python.org> > Since it's (potentially) a pretty small feature I might be convinced > to accept it in beta2, but I don't want the fact that it was committed > to force our hand. Raymond, if you care about this feature, please > roll it back so we can have a proper discussion without pressure. > > -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4