> When that happens, I hope that comparisons between long and float > will either raise TypeError or behave as if they are done in > infinite precision. Right now, the long gets converted to float, > which may lose precision; as a result, it is possible to have values > such that a==b, b==c, and a!=c. I agree that doing them as if usin infinite precision is best, but I adamantly oppose the idea that they should not be comparable at all. To the contrary, we should do our best to ensure that int/long are properly and cleanly embedded in floats. That's why I introduced the change to int/long division after all. --Guido van Rossum (home page: http://www.python.org/~guido/)
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