We've observed in our previous operating system, RHEL6, that most users want cutting edge Python packages. This version relies on locally installed packages, most of which also come from RPMs, some of which are usually somewhat outdated. Now load the module for Python 3.*, and try again (note for python 3, you will need to use the 'python3' ~]# module load ~]# which ~]# python3 -VĬentOS 7 comes with /usr/bin/python (version 2.7). Observe the effect of the module ~]# which python But if you have pre-existing code that uses, for example, '#!/usr/bin/env python', you will want 'python' to point to the right version.

For example, /usr/local/bin contains 'python#.#' for each specific version. The most significant advantage to using a module file is that the command 'python' becomes associated with the appropriate binary.

You may use whichever you prefer or find more convenient. We've configured our CentOS 7 system to be compatible with either usage of /usr/local/bin symlinks, or with module files. To understand what effect running a module file has, see it's corresponding module file in /usr/local/etc/modulefiles/. stow/python-3.*/bin/python3.*Īlternatively, you can load each version of Python's respective module (see Module System): These are symlinks to their full installation trees in /usr/local/stow/.

In most cases, you'll want to use one of our custom-built installations: There are several options for using Python in CentOS 7. For example, in python 3.*, the * could be substituted for 6 for Python 3.6, and so on. * refers to any available minor version of the major version (Python 2 and Python 3 are major).

Install pip centos 7