[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Mark Lawrence breamoreboy at yahoo.co.uk
Mon Mar 10 23:35:29 CET 2014
- Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Next message: [Python-Dev] Python 4: don't remove anything, don't break backward compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]