[Guido] > Using decimal floating point won't fly either, [Tim] > If you again mean "by default", also agreed. [Greg Ewing] > But if it's *not* by default, it won't stop naive users > from getting tripped up. Naive users are tripped up by many things. I want to stop them in *Python* from stumbling over 1/3, not over 1./3 or 0.5. Changing the meaning of the latter won't fly, not at this stage in the language's life; if the language were starting from scratch, sure, but it's not. I have no idea why Guido is so determined that the *former* (1/3) yield binary floating point too (as opposed to something saner, be it rationals or decimal fp), but I'm still trying to provoke him into explaining that part <0.5 wink>. I believe users (both newbies and experts) would also benefit from an explicit way to spell a saner alternative using a tagged fp notation. Whatever that alternative may be, I want 1/3 (not 1./3. or 0.5 or 1e100) to yield that too without futzing with tags.
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