> Except if Django has a Python 3.0 version, say, this fall, that means > how many years of supporting two parallel versions of Django and > merging features and fixes back and forth between them?
Please see my recent report: 0 years, 0 months, 0 days, 0 seconds. You can (probably) support Python 2.x and Python 3.x out of a single source tree. > And if the > initial port isn't supported that long, don't we just get to port all > over again down the line? If the porting strategy is used that I'm proposing, the worst thing that may happen is that the 3.x support in Django suffers from bitrot, but it won't be wasted if people start picking it up again. More likely, people occasionally try it out again, and prevent bitrot by providing fixes. Regards, Martin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
