RetroSearch Browse

Thu Sep 14 00:04:46 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-September/068771.html

Thanks for the link - it's a good explanation.

FYI I've opened a bug against the VC++ team to fix their round tripping on floating point values (doesn't sound like it'll make the next release, but hopefully it'll make it someday).

-----Original Message-----
From: Tim Peters [mailto:tim.peters at gmail.com]
Sent: Wednesday, September 13, 2006 11:39 AM
To: Dino Viehland
Cc: python-dev at python.org; Haibo Luo
Subject: Re: [Python-Dev] .pyc file has different result for value "1.79769313486232e+308" than .py file

[Dino Viehland]
> We've noticed a strange occurance on Python 2.4.3 w/ the floating
> point value 1.79769313486232e+308 and how it interacts w/ a .pyc.  Given x.py:
>
> def foo():
>         print str(1.79769313486232e+308)
>         print str(1.79769313486232e+308) == "1.#INF"
>
>
> The 1st time you run this you get the correct value, but if you reload
> the module after a .pyc is created then you get different results (and
> the generated byte code appears to have changed).
> ...

Exhaustively explained in this recent thread:

http://mail.python.org/pipermail/python-list/2006-August/355986.html

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-September/068771.html below:

[Python-Dev] .pyc file has different result for value "1.79769313486232e+308" than .py file