Furthermore, there are other languages like Scala which broke people's code at every release, and they are still being used and haven't seen that much fragmentation.
On Fri, Nov 27, 2015 at 7:17 PM, Russel Winder <[email protected]> wrote: > On Thu, 2015-11-26 at 21:05 +0100, Guillaume Laforge wrote: > […] > > compatibility, but the differences between Python 2 and 3 were much > > bigger > > that what we're speaking about here. > > It is time to put this Python 2 to Python 3 bogeyman into the dustbin > of history. With Python 3.3 and later conversion of Python 2.7 codes to > Python 3.x (x ≥ 3) codes is relatively straightforward unless your code > is fundamentally based on a string of length 1 being a 8-bit byte > (which is why Mercurial has a problem). No other Python 2 codes have a > problem other than intransigence of the programmers. > > -- > Russel. > > ============================================================================= > Dr Russel Winder t: +44 20 7585 2200 voip: > sip:[email protected] > 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder > > -- Guillaume Laforge Apache Groovy committer & PMC member Product Ninja & Advocate at Restlet <http://restlet.com> Blog: http://glaforge.appspot.com/ Social: @glaforge <http://twitter.com/glaforge> / Google+ <https://plus.google.com/u/0/114130972232398734985/posts>
