-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[pip 1.0] No such file or directory: ... installed-files.txt #373
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
Comments
I stumbled across this bug because I was also trying to use --root with pip. After searching around, I realized that I really wanted to be using --prefix instead of --root (see Python issue 8357 for a description of the difference). I thought I'd comment here in case other people were making my same mistake. Pip works as expected with --prefix. |
I'm going to close this since it's very old and I can't seem to reproduce. |
@dstufft, sounds like I'm running into exactly the same problem with latest pip on Ubuntu 14.04 with stock Python 2.7, and only when installing from git, normal instal from PyPI works just fine:
|
I encountered this issue too, when installing to a
|
I encounter this issue, too. Using
|
I can reproduce this issue when using Python installed via Homebrew on macOS.
This is not limited to Werkzeug. It does not happen when I use Ths method of installation is related to Homebrew setting the |
The solution mentioned in this StackOverflow answer, works. I wonder then, why Edit It breaks installations without |
Found a command to reproduce this issue on Windows. Pip version is 9.0.1. Using the
|
I can reproduce this issue on my debian VPS, too
Edit 19.05.2017 -- Added missing quotes to pip install command and |
Hi everyone! I am trying to reproduce this issue in an attempt to debug it but am unable to reproduce it. Could someone who is able to reproduce this issue provide the steps to how they encountered it? |
Since I couldn't reproduce that issue and test the patch I made, could someone who can reproduce it please try to see if this patch resolves the issue? |
I can confirm that the issue is fixed for the above command. Thanks! Seeing the trivial nature of the changes in #4495, I think it is safe to assume that it is also fixed the general case. Any idea when Pip 9.0.2 will hit the mark? So I can make my package depend on it. :-) |
I encountered this error when running |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The text was updated successfully, but these errors were encountered: