[Python-Dev] Python 4: don't remove anything, don't break backward compatibility (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Mon Mar 10 23:28:33 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 ]
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. :-(
-- Greg
- 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 ]