On Fri, Mar 28, 2008 at 8:07 PM, Daryl Spitzer <[EMAIL PROTECTED]> wrote: > On Fri, Mar 28, 2008 at 8:57 AM, Jacob Kaplan-Moss > > Ahh -- this was the part I was missing; my apologies for being dense. > > I've been thinking of 2to3 as a one-time tool -- run it to move to > > 3.0, and never look back -- not as part of a distribution process. > Unless I'm missing something, wouldn't Django likely have to include > code that would only work on 2.6 for this to work?
As far as 2to3 is involved, you are supposed to modify the python 2.5 code until 2to3 gives perfect conversion, not play with the results. The goal is to prepare the code so the future move involves running one tool, not to convert now and drop 2.5 support. So the only way this could work is to alter possibly ambiguous 2.5 code and watch the diffs generated by 2to3 without actually switching to python 2.6/3.0. -- Patryk Zawadzki PLD Linux Distribution --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
