James Bennett wrote: > Apologies for the length of this email, Thanks, James, for your post-doctoral dissertation on the History and Cumulative Predicted Future of Python Versions and Their Interrelations With the Django Development Process. :-) (joking aside, it was an appreciated and well-researched post)
For the most part, I give a +1 to James's plan of action. The only item I'd tweak is giving hard cut-off correlations between Django versions and Python version. Just as his Hunt for Red October example shows, Python shouldn't be *forcing* Django to bump up the supported version number, but rather making developers *want* to drop support. It seems the current catalyst for the "drop 2.3" thread is that 2.3 has baggage associated with it that keeps Django from evolving as rapidly as developers want. Whether decorator syntax, built-in sets, generator syntax, performance issues, bugs related to 2.3'ness, testability, or whichever other aspect that 2.3 lacks, it's putting a drain on developers to be backwards compatible. And from the dialog on this list, there's a clear developer *want* to drop 2.3 However, I haven't seen any/much expression of *want* that 2.4 be dropped any time in the near future (and there are a much larger number of 2.4 deployments). I wouldn't schedule that "2.4 will be dropped in Django 1.3" timetable, but rather a similar lead-up process as 2.3 has experienced -- a JKM post of "dropping 2.4 support. Discuss" when 2.4 starts causing enough problems to be more trouble than it's worth. So I'm somewhere between -0 and -1 on the voting scale regarding forced/long-range Python-version deprecation. But when a version becomes sufficiently dead weight, slowing down Django's progress like 2.3 seems to be doing, I'm +0 to +1 on dropping it with one Django-version worth of notice. Once the decision has been made, release one last Django version with a "this is the last version of Django to support Python version X" notice (judicious timing of the discussion-to-drop shortly after an official Django release would help). My 2.8571428571428573e-11 of the $700-billion bailout... -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
