On Sep 5, 2013, at 7:43 AM, Russel Winder <[email protected]> wrote:
> On Thu, 2013-09-05 at 10:12 +0000, Tom Tanner (BLOOMBERG/ LONDON) wrote:
>> Those of us who aren't so active and are still on python 2.6 are going to be
>> less happy, especially if we aren't entirely in control of which version of
>> python we get to use.
>
> << I thought I had replied to this, but cannot see it. If an earlier
> version turns up, sorry for the duplication. >>
>
> RHEL appears determined to stay with Python 2.6 and I guess many other
> have to as well. I was originally for the 2.7 floor to get at all the
> backports of 3.3 stuff as and when. However if there are many SCons
> users in need of executing on 2.6, and now that we know many projects
> who are being Python 2 and Python 3 compliant are choosing 2.6, 2.7 and
> 3.3+ as their compliance list and succeeding (*), I wonder if SCons
> should revert the 2.7 floor decision and consider a 2.6 floor decision.
virtualenv to the rescue. Install python 2.7 in /usr/local, create an
scons virtualenv with it, and you're good to go.
--
Chris BeHanna
[email protected]
_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev
