[jace]

I don't know anyone who uses Python 3 in production. It's still seen as an experimental implementation.

[kracekumar]

In Arch linux python 3 is default, https://www.archlinux.org/news/python-is-now-python-3/

[emidln]

I've seen more installs of pypy in production than python3.

[msellout]

Not experimental, just that there are good libraries that aren't Py3k yet.

[melling]

I dont' know Python but I'm thinking about learning it. What's experimental about Python 3? I don't have any legacy reasons to start with 2.7. Why wouldn't I just start with 3?

[metaphorm]

there's nothing experimental about Python 3. its a stable release version and I think its already up to sub version 3.3.

HOWEVER, there are many important 3rd party libraries that have not yet been migrated to be fully compatible with Python 3. these libraries are far more important to writing real applications than the ability to use some newer syntactic constructs in Python 3.

[callahad]

> HOWEVER, there are many important 3rd party libraries that have not yet been migrated to be fully compatible with Python 3.

Are there any particular libraries blocking you? Numpy / SciPy, IPython, Requests, Django, Pyramid, Bottle, etc. have all been ported to Python 3.

[metaphorm]

South (database migration for django). Until django core has its own migration tool I won't be using it with Python 3.

PIL as well. similar reasons. django image fields are dependent on PIL.

Celery is still on Python 2 also, and while there are other message queues available, none of them is as easy to integrate with for an app that's already written in Python.

[dorolow]

To replace PIL you should try Pillow, a fork of PIL that is capable of running on py3k (and 2.x).

[wodow]

The Python 3 Wall of Superpowers / Shame lists them for you in order of downloads: http://python3wos.appspot.com/

[packetslave]

To be fair, Django only supports Python 3 as of 1.5, which was released a bit more than a month ago.