preface

Here I want to tell you that you can do what you want with the development environment, but you must not touch the online environment! Even if you reboot the online environment, you should think twice before you act! I made a mistake at the end of 2014 when I entered only one online environment in the company project yum update Command, and the deployed items will be gg. Now, I mentally upgraded python on a server and replaced the version that came with the system. As a result, the deployed python based things failed.

Recurrence

The current situation is that the direct input of python is inconsistent with the/usr/bin/python version

 [ root@host  ~]# python -V Python 2.7.3 [ root@host  ~]# /usr/bin/python -V Python 2.6.6

I changed the soft connection of python to/usr/bin/python, which is still useless

Pit filling

I found a problem in the early morning of last night, so I wanted to solve this problem and go to sleep. But I really didn't have enough brains to solve it. I didn't find anything in StackOverflow that was the same as me. Is this pit too small?
After sleeping and thinking about this matter carefully, let's take a look at the path of python:

 [ root@host  ~]# which python /usr/local/bin/python

Surprised! The python path was originally in /usr/local/bin/ Folder, not in /usr/bin/ in Ok, change the soft link and see the version again.

 [ root@host  ~]# python -V Python 2.6.6

Finish it.

Last modification: January 23, 2018
If you think my article is useful to you, please feel free to appreciate it