It is actually so that with using __future__ and >=2.6 you already have most of the things available from Python 3 e.g. print() rather than print. See table at the bottom of
http://docs.python.org/dev/library/__future__.html#module-__future__ Sure, everybody is raving about Python 3 but 2.6 being the smallest supported version with Django would already be a huge leap towards 3 I think. As Russell said, looks like RHEL is going to be the indicator as to when things will move forward. If I look at http://distrowatch.com/table.php?distribution=redhat however and assume that RHEL 5.5 is going to be supported for quite some time then I think it might be a long time until Django arrives at 2.6 being the smallest supported Python version. How long are we going to plan supporting RHEL 5.5 and thus Python 2.4 after RHEL is out? -- 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.
