get-pipsi custom Python broken

Repository metrics

Stars

1,994 stars (1,994 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

Description

$ curl https://raw.githubusercontent.com/mitsuhiko/pipsi/master/get-pipsi.py | python3
...
Installed pipsi binary in /Users/apikeas/.local/bin
pipsi is now installed.
$ pipsi install saws
Running virtualenv with interpreter /Users/apikeas/.local/venvs/pipsi/bin/python3.6
Using base prefix '/usr/local/Cellar/python3/3.6.1/bin/../Frameworks/Python.framework/Versions/3.6'
New python executable in /Users/apikeas/.local/venvs/saws/bin/python3.6
Also creating executable in /Users/apikeas/.local/venvs/saws/bin/python
ERROR: The executable /Users/apikeas/.local/venvs/saws/bin/python3.6 is not functioning
ERROR: It thinks sys.prefix is '/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6' (should be '/Users/apikeas/.local/venvs/saws')
ERROR: virtualenv is not compatible with this system or executable
Failed to create virtualenv.  Aborting.

Contributor guide

Research direction

Investigate why the virtualenv created with the custom Python interpreter from get pipsi fails when using python3 but works with python. Trace the virtualenv creation logic and check for hardcoded paths or interpreter detection issues.

Tech stack

python

Domain

backend

Issue type

Bug

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.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

Python

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75