mitsuhiko/pipsi

Upgrading pip in virtualenvs managed by pipsi

Open

#72 opened on Mar 6, 2016

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Python (135 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (1,994 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I just spent a small amount of time wondering why pip would nag me to upgrade while using pipsi after I had already upgraded my system pip and the pip in the pipsi virtualenv. I finally realized that you need to upgrade pip in every single virtualenv (which is pretty obvious in hindsight, but well).

It would be nice if pipsi could offer a command to upgrade pip in a selected managed virtualenv, or in all managed virtualenvs at once.

Contributor guide

Research direction
Implement a command to upgrade pip in selected or all virtualenvs managed by pipsi. Look at pipsi's virtualenv management code to understand how to locate and modify virtualenvs.
Tech stack
python
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Pythonpip
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65