undefined | Better HN

0 pointsmetaphorm12y ago0 comments

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.

0 comments

callahad12y ago

> 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.

metaphormOP12y ago

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.

dorolow12y ago

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

wodow12y ago

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

packetslave12y ago

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

j / k navigate · click thread line to collapse