A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2008-June/080747.html below:

[Python-Dev] [Python-checkins] r64424 - inpython/trunk:Include/object.h Lib/test/test_sys.pyMisc/NEWSObjects/intobject.c Objects/longobject.cObjects/typeobject.cPython/bltinmodule.c

[Python-Dev] [Python-checkins] r64424 - inpython/trunk:Include/object.h Lib/test/test_sys.pyMisc/NEWSObjects/intobject.c Objects/longobject.cObjects/typeobject.cPython/bltinmodule.c [Python-Dev] [Python-checkins] r64424 - inpython/trunk:Include/object.h Lib/test/test_sys.pyMisc/NEWSObjects/intobject.c Objects/longobject.cObjects/typeobject.cPython/bltinmodule.cRaymond Hettinger python at rcn.com
Thu Jun 26 23:30:43 CEST 2008
[MvL]
>> Then I'd argue that the feature should be symmetric: 
>> If there is support for printing floating point numbers 
>> as hex, there should also be support for hex floating 
>> point literals.

[Mark]
> I agree with this.  Or at least support for hex floating point
> strings, if not literals.

ISTM, that the currently proposed output format gives
us this benefit for free (no changes to the parser).  
The format is already close to the C99 notation 
but replaces the 'p' with '* 2.0 **' which I find to
be both readable and self-explanatory.


Raymond
More information about the Python-Dev mailing list

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