-
Notifications
You must be signed in to change notification settings - Fork 304
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
Pip fails to install into clean virtualenv. #20
Comments
fake-name
changed the title
pip no longer installs into unsourced virtualenvs
Pip failing to install into virtualenv.
Apr 15, 2018
fake-name
changed the title
Pip failing to install into virtualenv.
Pip failis to install into clean virtualenv.
Apr 15, 2018
fake-name
changed the title
Pip failis to install into clean virtualenv.
Pip fails to install into clean virtualenv.
Apr 15, 2018
Ok, running it with Apparently:
Closing in favour of those. |
This is a dupe of #19 and can be closed. |
Heh. |
fake-name
added a commit
to fake-name/AutoTriever
that referenced
this issue
Apr 15, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This happened approximately 12 hours ago.
I have a deploy script which has the following snippet:
Prior to 12 hours ago, this worked.
Currently, this fails on
./venv/bin/pip install six
, because./venv/bin/python3 get-pip.py
no longer results in the./venv/bin/pip
file being created.Sourcing the venv prior to installing pip also fails to result in a proper install.
I can reproduce this reliably.
Platform: Ubuntu 14.04 LTS, Python 3.4.3.
The text was updated successfully, but these errors were encountered: