+1 I thought there was an implicit understanding that only 3 versions of Python would be supported at any given time. If so it makes sense to drop support for 2.4 when we add 3.x.
On Sat, Dec 10, 2011 at 9:22 AM, Jannis Leidel <lei...@gmail.com> wrote: > > I propose that we attempt to merge the py3k work after the release > > of 1.4, rather than let it go stale and lose the good work done so far, > > and also drop support for Python 2.5 for Django 1.5. > > +1 > > I think dropping Python 2.5 in the process of porting Django to Python 3.X > are reasonable goals. That said, even without the Py3k work going so well I > would support dropping Python 2.5 in the next major version. > > Jannis > > -- > 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 > 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-developers@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.
