Linux workstation

Upstream software project

python-virtualenv

Virtual Python Environment builder

About python-virtualenv

Virtual Python Environment builder

This project links 7 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

Debian 12 (Bookworm): 2 package records; Debian 13 (Trixie): 2 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.python-virtualenv: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)2 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
python-virtualenv
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, opensuse-leap-16-0, opensuse-tumbleweed
License expression
MIT
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

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. 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).

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. python3-virtualenv

    Debian 12 (Bookworm) / python / source python-virtualenv

    20.17.1+ds-1

    Python virtual environment creator

    allbookworm
  2. virtualenv

    Debian 12 (Bookworm) / python / source python-virtualenv

    20.17.1+ds-1

    Python virtual environment creator (Dependency package)

    allbookworm

Debian 13 (Trixie)

  1. python3-virtualenv

    Debian 13 (Trixie) / python / source python-virtualenv

    20.31.2+ds-1+deb13u1

    Python virtual environment creator

    alltrixie
  2. virtualenv

    Debian 13 (Trixie) / python / source python-virtualenv

    20.31.2+ds-1+deb13u1

    Python virtual environment creator (Dependency package)

    alltrixie

openSUSE Leap 16.0

  1. python313-virtualenv

    openSUSE Leap 16.0 / Unspecified / source python-virtualenv

    20.29.3-160000.3.1

    Virtual Python Environment builder

    noarchleap-16.0

openSUSE Tumbleweed

  1. python313-virtualenv

    openSUSE Tumbleweed / Unspecified / source python-virtualenv

    21.3.3-1.3

    Virtual Python Environment builder

    noarchtumbleweed
  2. python314-virtualenv

    openSUSE Tumbleweed / Unspecified / source python-virtualenv

    21.3.3-1.3

    Virtual Python Environment builder

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.