On 10/03/2014 22:28, Greg Ewing wrote: > Chris Angelico wrote: >> Terrible idea. Would wreak havoc with comparisons. No. Python 3 is all >> about Unicode, so the right way to proceed is 3.8, 3.9, 3.:, 3.;, 3.<, >> 3.=, 3.>, 3.?, 3.@, 3.A. > > And we have all of UCS-4 to play with, so for all > practical purposes the 3.x line can live forever! > > The downside is that we'll get endless complaints > from jmfauth about the Flexible Version Number > Representation. :-( > Drat, drat and double drat, you beat me to it :) -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
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