How to Install and Uninstall python2-virtualenv-clone Package on openSUSE Leap

Last updated: November 08,2024

1. Install "python2-virtualenv-clone" package

In this section, we are going to explain the necessary steps to install python2-virtualenv-clone on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install python2-virtualenv-clone

2. Uninstall "python2-virtualenv-clone" package

This tutorial shows how to uninstall python2-virtualenv-clone on openSUSE Leap:

$ sudo zypper remove python2-virtualenv-clone

3. Information about the python2-virtualenv-clone package on openSUSE Leap

Information for package python2-virtualenv-clone:
-------------------------------------------------
Repository : Main Repository
Name : python2-virtualenv-clone
Version : 0.5.4-bp153.1.16
Arch : noarch
Vendor : openSUSE
Installed Size : 37,5 KiB
Installed : No
Status : not installed
Source package : python-virtualenv-clone-0.5.4-bp153.1.16.src
Summary : Script to clone virtualenvs
Description :
virtualenv cloning script.
A script for cloning a non-relocatable virtualenv.
Virtualenv provides a way to make virtualenv's relocatable which could then be
copied as we wanted. However making a virtualenv relocatable this way breaks
the no-site-packages isolation of the virtualenv as well as other aspects that
come with relative paths and '/usr/bin/env' shebangs that may be undesirable.
Also, the .pth and .egg-link rewriting doesn't seem to work as intended. This
attempts to overcome these issues and provide a way to easily clone an
existing virtualenv.
It performs the following:
- copies sys.argv[1] dir to sys.argv[2]
- updates the hardcoded VIRTUAL_ENV variable in the activate script to the
new repo location. (--relocatable doesn't touch this)
- updates the shebangs of the various scripts in bin to the new python if
they pointed to the old python. (version numbering is retained.)
it can also change '/usr/bin/env python' shebangs to be absolute too,
though this functionality is not exposed at present.
- checks sys.path of the cloned virtualenv and if any of the paths are from
the old environment it finds any .pth or .egg-link files within sys.path
located in the new environment and makes sure any absolute paths to the
old environment are updated to the new environment.
- finally it double checks sys.path again and will fail if there are still
paths from the old environment present.