3 ms·
As I've said pretty consistently: getting Django onto Python 3 is not a technical code-porting issue. In fact, experimental Django-on-Python-3 branches exist an
by ubernostrum 15y ago
As I've said pretty consistently: getting Django onto Python 3 is not a technical code-porting issue. In fact, experimental Django-on-Python-3 branches exist and, so far as I'm aware, run pretty well.
The problem is and continues to be the social and community issue of gracefully deprecating our way out of Python 2.x, which we're basically doing at a rate of one Python version per Django release. All the patches in the world can't really make this process go faster :)
- overshard 15y agoAnd this is understandable, but as long as the branches for 3.x Django are "experimental" or created by a third party I'm not willing to put them into a stable production environment. Maybe Django just needs to come up with a 3.x branch to develop as stable along side the 2.x branch till 2.x starts to die out?