Message212921
Mark, we kinda proved we're willing to break backwards compatibility in the name of improving usability when we embarked down the path of creating Python 3 and an associated transition plan from Python 2, rather than just continuing to develop Python 2.
Compared to some of the backwards compatibility breaks within the Python 2 series that were handled using the normal deprecating cycle (removing string exceptions, anyone?), this one would be truly trivial. |
|
Date |
User |
Action |
Args |
2014-03-08 04:39:02 | ncoghlan | set | recipients:
+ ncoghlan, lemburg, tim.peters, skip.montanaro, georg.brandl, mark.dickinson, belopolsky, pitrou, eric.araujo, alex, r.david.murray, cvrebert, Alexander.Belopolsky, BreamoreBoy, ethan.furman, westley.martinez, gwrtheyrn, Lakin.Wecker, yselivanov, shai, dstufft, Andreas.Pelme, Amber.Yust, Hanxue.Lee |
2014-03-08 04:39:02 | ncoghlan | set | messageid: <1394253542.17.0.437046969153.issue13936@psf.upfronthosting.co.za> |
2014-03-08 04:39:02 | ncoghlan | link | issue13936 messages |
2014-03-08 04:39:01 | ncoghlan | create | |
|