The process that you describe inmsg85741 is a way of ensuring"memcmp(&x, &y, sizeof(x))==0", and it's portable and safe and is theRight Thing that we all want and expect. But that's not "x==y", as thatSun paper explains. It's close, but not technically accurate, as theimplication arrow only goes one way (just as "x=1/y" implies "xy=1" inalgebra, but not the other way around)I'd be interested to see if you could say that the Python objectmodel/bytecode interpretation enforces a certain quauntum of operationsthat actually does imply "eval(repr(x))==x"; but I suspect it'sunprovable, and it's fragile as Python grows to have more support inCLI/LLVM/JVM backends. My pedantic mind would strip any and all references to floating-pointequality out of the docs, as it's dangerous and insidiously misleading,even in "obvious" cases. But, I'll stop now :) (FYI: I've enjoyed the~100 messages here.. Great stuff!)