On Wed, 2010-10-06 at 18:53 +0800, Russell Keith-Magee wrote: > Now, one possibility is to say "Suck it up and upgrade your Python > version", but I'd rather consider that as a last resort.
I guess that's what I'm rather inclined to say :-) . You could argue that if we include the Python 2.5 logging module, then we are insulating people from the reality of their outdated Python installations, which is not doing them or the Python community any favours. I think Django should be doing the opposite - being a driving force to force distributions to support newer versions of Python. The only compelling argument against this IMO is the loss of functionality in the HTTP 500 e-mails relative to Django 1.0 to 1.2. I guess this would be the first time we said "We support Python 2.4, but now only partially support core feature X" - we would have to change the answer to this question: http://docs.djangoproject.com/en/dev/faq/install/#do-i-lose-anything-by-using-python-2-4-versus-newer-python-versions-such-as-python-2-5-or-2-6 In the past, there was the case of contrib.gis, which wasn't supported under 2.3 and was mentioned under that question, so I guess there is some precedent for this kind of thing, but I can see the argument against. Luke -- "Dysfunction: The only consistent feature of all of your dissatisfying relationships is you." (despair.com) Luke Plant || http://lukeplant.me.uk/ -- 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.
