> From the Django roadmap for supporting 3.0, using 2.6 as a stepping > stone (and if 2.7 was a *better* stepping stone then it would make it > easier): > > http://groups.google.com/group/django-developers/msg/0888b1c8f2518059?
Is that still a current plan? It's from November 2008. > This gets us to a situation where, about a year after the release of > Python 3.0, Django will be ready to make the transition -- the only > 2.x Python we'll be supporting is Python 2.6, and 2to3 plus manual > effort and available supporting libraries should make it possible to > also run Django on Python 3.0 either at that point or not long after. > > From there, 2.6 support can be dropped whenever convenient, and Django > can move to running only on Python 3.x at whatever time is judged > appropriate. I would claim that this specific plan was ignoring opportunities for migrating to Python 3.0. My Django port demonstrates that you can very well support 2.3 and 3.0 simultaneously: http://wiki.python.org/moin/PortingDjangoTo3k Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
