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.
Comments
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.
To replace PIL you should try Pillow, a fork of PIL that is capable of running on py3k (and 2.x).