Shared publicly  - 
Benjamin Root's profile photoDerek Hohls's profile photoRalf Haring's profile photoJoe Abbate's profile photo
Is it a coincidence that it's PEP 404. Not found?
"Multiple spellings

"There are many cases in Python 2 where multiple spellings of some constructs exist, such as repr() and backticks, or the two inequality operators != and <>. In all cases, Python 3 has chosen exactly one spelling and removed the other (e.g. repr() and !=were kept)."

Holy cow, imagine if they did that for Perl!
Sounds like it's time to start loving Python 3.
I don't think I can love it, but I can observe approvingly.
Python 3 is great and the major projects are finally moving over to Python 3, so I am glad that the 2.8 thing is getting buried once and for all.
It was about time. Three cheers for the great decision.
Darn, I guess I finally have to stop writing Python 2 code... :-D
And this is why I am glad that I made the decision to switch over to Python3, I knew that it was bound to happen and I welcome the change.
"And Now For Something Completely Different" that made me LOL
-1, no 2.8 is throwing out an opportunity to make a close as possible 2/3 interpreter. Until django does, so do I.
this will make it easy for me. I haven't started to learn python yet haha. Perfect time to jump in it sounds like :)
Glad to hear this, since I just committed to Python 3
It was bound to happen, honestly prefer to rip off the band-aid now than to keep prolonging it. See you guys on Python 3 :)
Rick K
What is python?
April's fools jokes are early this year ?
common people , move to python 3, wherever possible.
+Vasu Jaganath Well, if we are going musical ...we should all be living in the love of the common people (er, programmers?)
Just realize that major packages like maya and nuke only use 2.x, so you have cut a lot of us off from being able to move pipeline tools until those DCC apps do.
+Alexander Morano No one is "cutting" anyone off... Python 2.7 is still around and will still be supported. Packages that are slower to move will delay those communities still using them, of course, but the domino effect has begun.
And we need few millions of monkeys to move existing software to Python 3, because authors don't give a hoot to be transparently backward compatible. Well, or continue develop in Ruby instead.
Meh.. I still don't see the point of investing my time on porting to Python 3. I guess I'll stick to 2.7 regardless of the effort of killing the 2.x series.
Dear Guido,
Looks doable... The string stuff is really nice.
+Derek Hohls That post is over 3 years old, when Python 3 was first released. I'm curious as to how long (roughly) did the transition from Python 1 to 2 take and whether 2 broke backward compatibility with 1. Since there's more Python software now than then (one or two orders of magnitude, maybe?), it seems reasonable to expect that it will take two to three times as long to transition from 2 to 3.
Next release of matplotlib will support 2.6, 2.7, and 3.x. All is peachy!
+Joe Abbate I think Guido is the best person to ask for dates! But I think estimating a "transition from Python 1 to 2" might be difficult to estimate. I do think that as soon as the widely-used modules do this, most programmers will follow.
+Derek Hohls I've figured how to answer my own question. According to Guido's, Python 2.0 came out in October 2000. According to, the transition between Python 1 and 2 on Debian occurred when woody (3.0) was released (in July 2002) or roughly two years after. My prediction was the transition between Python 2 and 3 will take 2-3 times as long, so the timeframe would be year-end 2012 through year-end 2014. It's unlikely that Python 3 will be the default on wheezy (7.0), particularly since Django with Py3k probably won't be ready by then, so we're looking at 2013 or later.
Add a comment...