pypa/virtualenv

Virtual Python Environment builder

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 13th, 2026
Created on March 6th, 2011
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 1,115
Total Stargazers: 5,044 (+0)
Total Subscribers: 161 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.2 hours
Mean response time: 38.8 days
90th percentile: 43.3 days
Tracked items: 133

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 13% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (82)
  • help-wanted (36)
  • enhancement (25)

Most active issues this week

Detailed Description

virtualenv is a tool for creating isolated Python environments.

The tool solves the problem of dependency conflicts and environment pollution by creating separate Python installations where packages can be installed without affecting the system Python or other projects. It works by building a self-contained directory structure that contains its own Python interpreter, standard library, and site-packages directory, allowing developers to install project-specific dependencies in isolation.

Anyone working with Python should consider virtualenv if they need to manage multiple projects with different dependency requirements or want to avoid polluting their system Python installation. It suits any Python project from small scripts to large applications, and is particularly valuable in team environments where reproducible environments are essential. The tool supports multiple Python implementations including CPython, PyPy, and Jython, making it flexible across different runtime choices.

The project maintains active engagement with its issue tracker and accepts community contributions through established channels. Development follows the Python Software Foundation's Code of Conduct, establishing clear expectations for all interactions within the project community.