Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternative installation support / instructions #42

Closed
ericfrederich opened this issue Jan 23, 2017 · 2 comments
Closed

Alternative installation support / instructions #42

ericfrederich opened this issue Jan 23, 2017 · 2 comments

Comments

@ericfrederich
Copy link

Many prefer to keep their OS Python install clean of any 3rd party packages.
For others it's not even a choice as they don't have sudo access.

It would be nice to have instructions for an unprivileged user to get pipenv on their PATH in some way.

This seems hacky but it seems to work...

System with Python 3

python3 -m venv ~/bin/_pipenv
source ~/bin/_pipenv/bin/activate
pip install pipenv
ln -s ~/bin/_pipenv/bin/pipenv ~/bin

System with Python2 and virtualenv

virtualenv ~/bin/_pipenv2
source ~/bin/_pipenv2/bin/activate
pip install pipenv
ln -s ~/bin/_pipenv2/bin/pipenv ~/bin/pipenv2
@silvus
Copy link

silvus commented Jan 23, 2017

pipsi install pipenv ?

Pipsi

What does it do? pipsi is a wrapper around virtualenv and pip which installs scripts provided by python packages into separate virtualenvs to shield them from your system and each other.

pipsi installs each package into ~/.local/venvs/PKGNAME and then symlinks all new scripts into ~/.local/bin.

@kennethreitz
Copy link
Contributor

I think sticking to what we have currently is best — this is a tool like pip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants