Per the recent Red Hat Summit in Boston, RHEL7 willl be based off of Fedora 19, so yes: 2.7 will be the default /usr/bin/python in that distribution.
A related point of note: Python 2.6 is also easily installable on RHEL5 via EPEL (parallel-installable with the Python 2.4 release that shipped with RHEL). So, for both current major releases of RHEL/CentOS/Scientific Linux, Python 2.6 is a common denominator. (One could argue, though, that perhaps effort might be better-spent packaging Python 2.7 for EPEL6 much like 2.6 was back-ported to RHEL5 via EPEL, which would solve the problem for more projects than just Django. ;)) -Ed On Fri, Jun 28, 2013 at 12:22 PM, Clayton Keller <[email protected]>wrote: > On 06/28/2013 11:45 AM, charettes wrote: > >> If we drop support for Python 2.6 in Django 1.7 we should document that >> 1.6 will be the last version to support and announce it on the next >> beta/candidate release. >> >> Le vendredi 28 juin 2013 10:17:22 UTC-4, Aymeric Augustin a écrit : >> >> Hello, >> >> We just forked the stable/1.6.x branch. The development of Django >> 1.7 starts now! >> >> As far as I can tell, there's a consensus on dropping support for >> Python 2.6. That will allow us to remove the vendored copy of >> unittest2 and to take advantage of datastructures introduced in >> Python 2.7 like OrderedDict. >> >> I think we can continue supporting Python 3.2 in addition to Python >> 3.3 and 3.4. But if you see good reasons to drop it, I'd like to >> hear them! >> >> Thank you, >> >> -- >> Aymeric. >> >> >> > I just wanted to note that dropping Python 2.6 will drop the ability to > use RHEL 6 based installs without installing a second 2.7 instance of > Python. > > I believe RHEL 7 will provide Python 2.7 as its base package, but until > its release this deprecation could pose an issue for existing RHEL 6 users > wanting to stay current. > > I ask that you please keep this in mind. > > Clay > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > django-developers+unsubscribe@**googlegroups.com<django-developers%[email protected]> > . > To post to this group, send email to > django-developers@**googlegroups.com<[email protected]> > . > Visit this group at > http://groups.google.com/**group/django-developers<http://groups.google.com/group/django-developers> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- Ed Marshall <[email protected]> Felix qui potuit rerum cognoscere causas. http://esm.logic.net/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
