Re:Viewing Python 3.2 as the successor to Python 2.7
by yummyfajitas on Friday October 29, 2010 @01:29PM
(#1848100)
Django will be a tricky beast to port due to the fairly large ecosystem.
For my web projects, I almost always use at least django, fabric, djang_extensions and django_piston. If even one of these is unavailable, I'm sticking to 2.7. I use other django libs as well, and python 3 doesn't offer me enough features to make losing those libraries worthwhile.
For my web projects, I almost always use at least django, fabric, djang_extensions and django_piston. If even one of these is unavailable, I'm sticking to 2.7. I use other django libs as well, and python 3 doesn't offer me enough features to make losing those libraries worthwhile.