openstack
/
diskimage-builder
Code Issues Proposed changes
diskimage-builder/diskimage_builder/elements/pip-and-virtualenv
History
Clark Boylan 559de43694 On suse the python2 dev package is python-devel 
This was previously defined as python2-devel (which is what rhel uses),
but the actual package name is python-devel. See:

  https://software.opensuse.org/package/python-devel

Change-Id: Id61e5b05772d10c32b33d3e70cb64d5ebdcba6e4
 		2017-06-21 15:52:05 +10:00
..
install.d/pip-and-virtualenv-source-install Trivial fix typos 2017-05-31 11:17:05 +07:00
test-elements Start at using CI mirrors for fedora/centos 2017-06-21 12:02:27 +10:00
README.rst Skip python3-virtualenv on <= trusty 2017-04-12 06:36:20 +10:00
element-deps Release 1.25.2 2017-02-02 11:20:00 +11:00
package-installs.yaml Release 1.25.2 2017-02-02 11:20:00 +11:00
pkg-map On suse the python2 dev package is python-devel 2017-06-21 15:52:05 +10:00
source-repository-pip-and-virtualenv Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00

README.rst

pip-and-virtualenv

This element installs pip and virtualenv in the image.

Package install

If the package installtype is used then these programs are installed from distribution packages. In this case, pip and virtualenv will be installed only for the python version identified by dib-python (i.e. the default python for the platform).

Distribution packages have worked out name-spacing such that only python2 or python3 owns common scripts like /usr/bin/pip (on most platforms, pip refers to python2 pip, and pip3 refers to python3 pip, although some may choose the reverse).

To install pip and virtualenv from package:

export DIB_INSTALLTYPE_pip_and_virtualenv=package

Source install

Source install is the default. If the source installtype is used, pip and virtualenv are installed from the latest upstream releases.

Source installs from these tools are not name-spaced. It is inconsistent across platforms if the first or last install gets to own common scripts like /usr/bin/pip and virtualenv.

To avoid inconsistency, we firstly install the packaged python 2 and 3 versions of pip and virtualenv. This prevents a later install of these distribution packages conflicting with the source install. We then overwrite pip and virtualenv via get-pip.py and pip respectively.

The system will be left in the following state:

  • /usr/bin/pip : python2 pip
  • /usr/bin/pip2 : python2 pip (same as prior)
  • /usr/bin/pip3 : python3 pip
  • /usr/bin/virtualenv : python2 virtualenv

(note python3 virtualenv script is not installed, see below)

Source install is supported on limited platforms. See the code, but this includes Ubuntu and RedHat platforms.

Using the tools

Due to the essentially unsolvable problem of "who owns the script", it is recommended to not call pip or virtualenv directly. You can directly call them with the -m argument to the python interpreter you wish to install with.

For example, to create a python3 environment do:

# python3 -m virtualenv myenv
# myenv/bin/pip install mytool

To install a python2 tool from pip:

# python2 -m pip install mytool

In this way, you can always know which interpreter is being used (and affected by) the call.

Ordering

Any element that uses these commands must be designated as 05-* or higher to ensure that they are first installed.