A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] .pyc file has different result for value "1.79769313486232e+308" than .py file [Python-Dev] .pyc file has different result for value "1.79769313486232e+308" than .py fileTim Peters tim.peters at gmail.com
Wed Sep 13 20:39:26 CEST 2006
[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
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