pyenv/pyenv-virtualenv

a pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 9th, 2026
Created on February 18th, 2013
Open Issues & Pull Requests: 93 (+0)
GitHub issues: Enabled
Number of forks: 428
Total Stargazers: 6,728 (+0)
Total Subscribers: 70 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.8 hours
Mean response time: 248.9 days
90th percentile: 993.9 days
Tracked items: 43

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 846 days
Stale 30+ days: 13
Stale 90+ days: 13

Recent activity

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

Top labels

  • need-feedback (6)
  • third-party (5)
  • by-design (3)
  • enhancement (1)
  • misconfiguration (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

pyenv-virtualenv is a pyenv plugin that manages Python virtual environments alongside multiple Python versions.

The tool solves the problem of coordinating Python version management with virtual environment isolation. Rather than requiring separate workflows for selecting Python versions and creating isolated environments, pyenv-virtualenv integrates both concerns into a single plugin. It allows you to create virtual environments tied to specific Python versions managed by pyenv, then activate them through pyenv's version-selection mechanism.

Developers working with multiple Python projects that require different Python versions should consider this tool. It suits teams that have already adopted pyenv for version management and want to avoid the friction of manually specifying which Python interpreter each virtual environment should use. The plugin is particularly valuable when you need to maintain several isolated environments across different Python versions without managing separate installation paths or complex shell configuration.

The project shows consistent maintenance with regular commits addressing bug fixes and compatibility updates. Pull requests receive timely review and feedback from maintainers. Issues are actively triaged and responded to, indicating ongoing engagement with user needs. The codebase demonstrates stability through incremental improvements rather than major architectural shifts.