Terry Reedy wrote: > The particular issue here is not platform dependence as such but > within-platform usage dependence, as in the same code giving radically > different answers in a standard interactive console window and an idle > window, or when you run it the first time (from xx.py) versus subsequent > times (from xx.pyc) until you edit the file again. Yet, this *still* is a platform dependence. Python makes no guarantee that 1e1000 is a supported float literal on any platform, and indeed, on your platform, 1e1000 is not supported on your platform. Furthermore, Python makes no guarantee that it will report when an unsupported float-literal is found, so you just get different behaviour, by accident. This, in turn, is a violation of the principle "errors should never pass silently". Alas, nobody found the time to detect the error, yet. Just don't do that, then. Regards, Martin
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