pyenv/pyenv-installer

This tool is used to install `pyenv` and friends.

View on GitHub ↗Jump to charts ↓Open shareable report →

pyenv/pyenv-installer has 4k+ stars and 450+ forks on GitHub, is written in Shell, and was last pushed on Oct 7, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 7th, 2026
Created on June 1st, 2013
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 452
Total Stargazers: 4,132 (+0)
Total Subscribers: 73 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.5 hours
Mean response time: 76.8 days
90th percentile: 409.6 days
Tracked items: 13

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

pyenv-installer is a shell script that automates the installation and setup of pyenv and its companion tools.

The tool solves the problem of getting pyenv up and running on a new system by handling the download and installation process in a single command. It requires only Git and the appropriate build libraries for your operating system, which the project documents in its installation wiki for common platforms. The installer itself is inspired by the rbenv-installer project and follows a similar pattern for managing Python version installations.

Developers should choose this tool if they want a streamlined way to bootstrap pyenv rather than manually cloning repositories and configuring shell environments. It suits anyone setting up pyenv on a fresh machine or CI environment where automation is valuable. The tool also handles updates and uninstallation through the same interface, making it useful for managing the pyenv installation lifecycle.

The project maintains a stable, minimal codebase focused on its core installation task. Development activity is sparse but consistent, with changes addressing specific issues rather than frequent feature additions. The project accepts contributions and maintains responsiveness to reported problems, though the pace of updates reflects the tool's mature and stable nature.