[CentOS] upgrading python

Tue Dec 12 14:17:11 UTC 2017
Larry Martell <larry.martell at gmail.com>

On Tue, Dec 12, 2017 at 9:11 AM,  <m.roth at 5-cent.us> wrote:
> Larry Martell wrote:
>> On Mon, Dec 11, 2017 at 4:32 PM, Larry Martell <larry.martell at gmail.com>
>> wrote:
>>> On Mon, Dec 11, 2017 at 4:25 PM, Clint Dilks <clintd at scms.waikato.ac.nz>
>>> wrote:
>>>> On Tue, Dec 12, 2017 at 10:09 AM, Larry Martell
>>>> <larry.martell at gmail.com>
>>>> wrote:
>>>>> On Tue, Dec 5, 2017 at 8:22 AM, Pete Biggs <pete at biggs.org.uk> wrote:
>>>>> > On Tue, 2017-12-05 at 14:16 +0100, Kai Grunau wrote:
>>>>> >> On 05.12.2017 14:05, Larry Martell wrote:
>>>>> >> > I am running CentOS 7 and I have python version:
>>>>> >> > Python 2.7.5 (default, Sep 15 2016, 22:37:39)
>>>>> >> > I need a newer version of 2.7 to pick up a bug fix. How can I do
>>>>> >> that (without breaking anything in CentOS)?
> <snip>
>>>>> > Or use Software Collections, the Python27 package from there has
>>>>> > 2.7.13
>>>>> >  https://www.softwarecollections.org/en/scls/rhscl/python27/
>>>>> >  https://wiki.centos.org/AdditionalResources/Repositories/SCL
>>>>>
>>>>> I followed the instructions at the first link and I still only seem to
>>>>> have 2.7.5. How can I specify a newer version?
>>>
>>>> Hi, perhaps reading https://www.softwarecollections.org/en/ and
>>>> https://www.softwarecollections.org/en/scls/rhscl/python27/ will help.
>>>>
>>>> Have you done scl enable python27 bash in your current shell?
>>>
>>> Thanks. Missed that. Now I do get 7.5.13 but it seems I have to type
>>> that command in each new shell. Can I make that the default python? I
>>> want django and uWSGI to use that version.
> <snip>
> I guess my very brief suggestion  wasn't understood: in whatever shell
> script you use to start the tools you want to use, insert, at the top,
> right under the #!/bin/bash, the line
>  . /opt/<path/to/python2.7>/enable
> so that the paths are set for that shell script, and all its children.
> This will not result in you going into python's command line, nor will it
> affect anything else, including yum.

Sorry, missed your previous post. Ended up that I had to reinstall
uWSGI using the 2.5.13 pip, and then link
/opt/rh/python27/root/usr/bin/uwsgi to /usr/bin/uwsgi. Now that I have
it running, hopefull it will resolve the issue I had (which was a bug
in the 2.7.5 zlib).