for the record, i -only- use py3. python 3.2 came out almost half a year ago and i deployed it on my pack of servers a couple months ago. everything i do is in 3.2 now. previously i used 3.1. i've ported a few projects to py3 for my own uses - tried to provide patches but many packages are dormant. our data centers have quite a mix of installations, even back to the ancient 2.4. it really isn't -that- hard to write code that runs on both 3.2 and 2.4. performance? i've heard that mention of the py3 running slower than py2, but that water went under the bridge a long time back and it seems to me more like a religious misdirection than a legitimate argument. it depends what you're doing and how you're doing it. i can make py2 code abysmally slow and py3 code scream. many of us py3 people have ported things already but there's such a stalwart opposition to updating, that we sound like a lonely broken record when we provide patches.
what's better in 3 than 2? i don't know off the top of my head. it's been forever since i wrote in py2 and i played with the "new and improved" in py3 so far back, that it's not new and improved any more, and used so frequently, that i couldn't set it apart from anything else. my current project is wsgi focused. py3 has a wsgi module built into it. it just works, beautifully. i store millions of rows of data in psql and generate a bunch of PDF and html reports based on thousands of servers. i've wanted to use web2py, but i don't have the free time at present and i don't have any of my server farm that runs py2 to bridge anything and i can't abscond with customer datacenter servers. so please don't think that nobody uses py3. you'll probably find very few people -here- talk about py3, mostly because your project doesn't support it and the general consensus seems to be that you'll get around to it - some day, as another project. if you spend all your time in the orange grove, you probably won't find many cherry trees. >:-} -david
