On Mon, Aug 1, 2016 at 10:56 AM, Connie Sieh <[log in to unmask]> wrote:
>> On Sat, 30 Jul 2016, P. Larry Nelson wrote:
>>
>>> Hi all,
>>>
>>> Please don't shoot the questioner (me), as I have no experience with
>>> Python, other than knowing "what" it is and that my SL6.8 systems have
>>> version 2.6.6 installed.
>>>
>>> I have been asked by one of our Professors that one of his grad students
>>> apparently needs Python 2.7.x installed on our cluster (optimally in
>>> /usr/local, which is an NFS mounted dir everywhere).

Never replace basic system components this way. If you ever have to do
this, put them in /usr/ocal/python27, or /opt/python27. This is very
much what the SCL tools published upstream by Red Hat do, and
available for Scientific Linux and CentOS.

This student and professor may want to think of jumping to SL 7, and
avoiding the issues with other legacy components.

>>> If the solution is indeed simple, I might proceed, otherwise, I'm
>>> of a tendency to reply to the Professor and student, "No way - won't
>>> work."
>>> I think the student probably has access to CERN systems that probably
>>> have what he's looking for.
>>
>>
>> I see that Larry's requirement may have gone away, but for others
>> with the same request:
>>
>> The slc6-scl "Software Collections Library" repo has a suite of packages
>> python27-* which can be installed alongside the system python 2.6.
>>
>> They also have python33-* although those who want python3 may
>> want bleeding edge which is, IIRC, 3.4.something.
>> (Hmm bleeding edge is 3.6.0a3, latest is 3.5.2).
>>
>
> Also in SL software collections via
>
> ftp://sldist.fnal.gov/linux/scientific/6x/external_products/softwarecollections/yum-conf-softwarecollections-1.0-1.el6.noarch.rpm