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

Last updated: November 23,2024

Deprecated! Installation of this package may no longer be supported.

1. Install "python2-virtualenv" package

This guide let you learn how to install python2-virtualenv on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                python2-virtualenv
            
                    
    
    Copied

2. Uninstall "python2-virtualenv" package

This guide covers the steps necessary to uninstall python2-virtualenv on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                python2-virtualenv
            
                    
    
    Copied

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

Information for package python2-virtualenv:
-------------------------------------------
Repository : Main Repository
Name : python2-virtualenv
Version : 16.1.0-1.13
Arch : noarch
Vendor : SUSE LLC
Installed Size : 2,1 MiB
Installed : No
Status : not installed
Source package : python-virtualenv-16.1.0-1.13.src
Summary : Virtual Python Environment builder
Description :
virtualenv is a tool to create isolated Python environments.
The basic problem being addressed is one of dependencies and versions, and
indirectly permissions. Imagine you have an application that needs version 1
of LibFoo, but another application requires version 2. How can you use both
these applications? If you install everything into
/usr/lib/python2.4/site-packages (or whatever your platforms standard location
is), its easy to end up in a situation where you unintentionally upgrade an
application that shouldnt be upgraded.
Or more generally, what if you want to install an application and leave it be?
If an application works, any change in its libraries or the versions of those
libraries can break the application.
Also, what if you cant install packages into the global site-packages
directory? For instance, on a shared host.
In all these cases, virtualenv can help you. It creates an environment that
has its own installation directories, that doesnt share libraries with other
virtualenv environments (and optionally doesnt use the globally installed
libraries either).