On Nov 16, 2004, at 4:00 AM, Greg Ewing wrote: > Delaney, Timothy C (Timothy) wrote: >> All this would just go away if in Python 3.0 (or even earlier ;) > > floats required something after the decimal point i.e. to get >> '<float 1.0>' you had to type '1.0' and '1.' by itself was a > > syntax error. > > I always write float literals that way anyhow, in the > interests of clarity. So I wouldn't mind if this > happened either. > > +0 I tend to use integer float literals without the trailing zero from the interpreter if I want float division to happen without typing "from __future__ import division". Having to type an additional character isn't a problem, though. +0 -bob
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