[yason]

I thought Python 3 was already D.O.A. I haven't seen anybody using it nor have I seen any compelling reason to start using it myself, or any reason at all to even keep it on my radar.

When v3 was announced, IIRC even the Python folks themselves actually suggested that people just continue with v2.x until later when v3 becomes mainstream and it never did. In fact, I was surprised to see negative criticism about Python 3. It seems to me that nobody has been using Python 3, and therefore not complaining about it either.

[briancurtin]

If it was dead on arrival, it has risen from the grave quite nicely. I previously linked to two sources showing it has pretty good signs of life: PyPI packages and download numbers (posted here: http://news.ycombinator.com/item?id=3323908).

When it was announced, people did suggest everyone continue on with 2.x, but not just until everyone waits for it to be mainstream (that clearly wouldn't work). No one expected users to drop everything and port right away. As your dependencies come up to speed with 3, try your project with them. Create an experimental branch. Do something to keep up. You don't need to halt your own progress for it, but you shouldn't sit on your hands.

I've been using Python 3 at work for around 2 years now, writing test frameworks and tools in a C++ environment (working on a historical tick database). While a lot of the web people are stuck on 2, and that has been changing for a while and it's only getting better there, a lot of other areas have been available to and have been using Python 3.

[sp332]

There's a 5-year roadmap, and we're about halfway through it. Many of the most popular libs are already available in Py3. For example Django just released a version supporting it. https://news.ycombinator.com/item?id=3305021

[briancurtin]

They didn't cut a release with it, yet. The work has been done and it is or will be in a branch, but it still needs to be reviewed and "accepted" in order to move on.

[jacobian]

It is, however, a question of "when", not "if".

[kamaal]

I don't have time to wait for "when", especially when there are working options right now.

I am going to use and encourage other to use things that work right now, than wait for something in the future which we aren't even clear of.

[jacobian]

That's awesome - write about what you do, please? The Python3 web world is still in its infancy, and I'm really interested to hear how it goes

[mathnode]

Blender is using Python 3.

I'll go and sit back down in my corner.

[redsymbol]

For what it's worth, my startup (Mobile Web Up) uses Python 3 almost exclusively. Our core product is basically a very specialized web server built on Python3+WSGI.

There are some rough edges still. Our (marketing) website runs on Django, using Python2.7. There's been enough progress Py3k support for django recently that I'm hopeful we can migrate that by mid-2012. And I'd love to have solid Py3k support for a couple more libraries, like boto for EC2/S3/AWS.

All in all, for the particular things we need, Python 3 is practical now. We have paying customers whose services run on software written in Python 3.

[baq]

when python 2 showed up, people kept using 1.5.2 for _years_.