The right way to transition according to Guido is to port to 2.6, run with warnings on, cover everything with unit tests, check if everything works right, run 2to3 to convert, see if everything is still alright, fix problems in 2.6, rerun 2to3, etc...
Since Django supports Python from 2.3, they'll probably have to branch of the 2.6/3 version. I expect it's not going to happen soon. On Tue, Jun 24, 2008 at 9:55 AM, Ed McCaffrey <[EMAIL PROTECTED]> wrote: > Hello, > > My project consists of a couple of stand-alone applications that gather and > process the data that the eventual Django-powered site will serve. I'm > seeing at least 6-8 months until work on the site will begin. > > Is there a plan for upgrading Django to Python 3.0? > > Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
