If you're going to use such an ancient version of a distribution, you are only crippling yourself. As you said yourself, you should move on; if someone is using Python 2.3, they can use Django 1.1/1.2. If they want all-new 1.3 features, then updating Python/distro should not be a roadblock.
This is a common issue in software backwards compatibility, and I'm at least one to think that just because someone, somewhere still uses an old version of python, they can't also keep using an old version of Django. J. Leclanche / Adys On Mon, Apr 5, 2010 at 9:55 AM, Dennis Kaarsemaker <den...@kaarsemaker.net> wrote: > On ma, 2010-04-05 at 14:37 +0800, Russell Keith-Magee wrote: > >> For some perspective - even though Python 3.1 is out, dropping support >> for Python 2.3 in Django 1.2 is being greeted as controversial in some >> circles because RedHat Enterprise Linux 5 is still officially >> supported by RedHat, and RHEL5 ships with Python 2.3. > > Rhel 5 ships with 2.4, rhel 4 shipped with 2.3. I still have to use > django on the latter, so the support for 2.3 being dropped is an issue > for me. Then again, rhel 4 is positively ancient and I really should > move on :-) > > -- > Dennis K. > > They've gone to plaid! > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
