Sure, so am I...privately. But all my serious work stuff is in Python 2, and no one is going to pay me to update it, so I cant't. Now I guess, if in a year or s

Sure, so am I...privately. But all my serious work stuff is in Python 2, and no one is going to pay me to update it, so I cant't. Now I guess, if in a year or so Python 3 will have gained back a few more features of Python 2, porting my stuff will finally be easy enough. I have to add though that maybe my use case is a bit unusual. I'm not a "professional developer", but a scientist. In our case the developers of our programs are the users, and everybody has to be able to edit them. So there is a lot of inertia to change. Also we do a lot of "crazy" things, like custom C modules, mixing Python/C(++), using Python as a description language for batch jobs, and so on. Previous updates were not trivial, but possible. But somehow we never managed to make the jump to Version 3 of anything. Hell, we just started to switch from SVN to git... What I'm trying to say is, it's kind of sad that there are all these cool "new" technologies and paradigms and we seem to be unable to pass the threshold to them. I see people around me alienated by Windows 8, Gnome, and so on, so instead of updating they stick with their old setup or switch to Mac, not because it is superior, but because it is the most conservative option. For the same reason we stick with old versions of Python, GCC, Red Hat, and so on. The only machines I can currently do my work on are my work PC with like 5 year old CentOS on it, or my Hackintosh at home, because stuff won't run on newer (non-OSX) systems. I guess I'm just a bit angry that I always suffer from these "Break the world, do the right thing, let's be bold" kind of upgrades. It's great for people living on the edge, who can pick themselves what they want to use. Other people have to wait for the goodness to trickle down, and that has been taking way to long in case of Python 3 for me.