RetroSearch Browse

Fri Jul 18 21:38:46 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-July/081406.html

Eric Smith schrieb:
> georg.brandl wrote:
>> Author: georg.brandl
>> Date: Fri Jul 18 13:15:06 2008
>> New Revision: 65099
>> 
>> Log:
>> Document the different meaning of precision for {:f} and {:g}.
>> Also document how inf and nan are formatted. #3404.
> 
> Thanks for doing this.  But see this output:
> http://www.python.org/dev/buildbot/all/sparc%20solaris10%20gcc%20trunk/builds/255/step-test/0
> which shows that on Solaris with gcc it's 'NaN', not 'nan'.  This is one 
> of the reasons I didn't get into documenting it.  And on Windows, it's 
> even worse (no Windows box handy, sorry).

I see.

> Do we want to document the actual behavior, or do we want to normalize 
> all platforms so that they all return 'nan' and 'inf'?

I'd find a consistent behavior nice, if it isn't too much work to
get one.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

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

Showing content from https://mail.python.org/pipermail/python-dev/2008-July/081406.html below:

[Python-Dev] [Python-checkins] r65099 - python/trunk/Doc/library/string.rst