'pip list -v' not showing correct locations of installed modules #5861
Comments
|
So pip is saying that all those packages (boto, boto3, botocore, ...) are installed in |
|
Yes, the 'dir' command above and 'pip list -v' were run at the same time.... there are many more packages shown with 'pip list -v', I'm pretty sure from my different venv. |
|
This is my venv directory: |
|
Did you rename the venv, or move it's location? |
|
'pip install' seems to work, but it's not in the current venv64 directory, and in the venv directory there aren't any new timestamps, so it's not installed there either. |
|
Don't use |
|
No, I didn't move the venv directory... I tried making a second venv (venv64 with 64 bit Python) but I can't install any modules into it. |
|
Why can't you install anything? Are you sure you're using the right pip? The one from the venv, and not one from your global Python installation? Check the output of |
|
yes, it seems to be.... |
|
OK, so after installing a package, what's the issue with using it? |
|
Note the fact that pip is installed as an egg is weird... That's not how it normally works. I know PyCharm does install packages as eggs, and this is known to cause issues. |
|
It's not showing in 'pip list -v' like that corenlp install for example... it installs 'successfully' but it's not really there. I'm sure I'm doing something wrong, but wondering if this is a bug in pip too. |
|
It's going to be difficult to debug further without the exact steps: starting with the command used to create the venv, how you activate it, ... Are you doing all this from PyCharm? |
|
Yes, I went into project settings to create it and point to a the 64 bit Python interpreter. Is there a way to see which directory in the 'install' command is using? Maybe with verbose? |
|
The more |
|
Ok, I tried that with an install, and minus the --ignore-installed flag Getting some lines like this(this is what I wanted to see in the verbose output): so an nltk directory looks like it's being created, but it's not really there. Later it removes corenlp that was never there: but then here fails (where it usually succeeds), but there's still nothing new in \venv64\Lib\site-packages |
|
That last error should be fixed in 18.1. |
|
What's the right way to switch the location of pip that is being used? I started a new Project in PyCharm, and made a new venv, but the old version of pip is being used still. |
|
I'm sorry, but I don't use PyCharm. Maybe try invoking pip using |
|
I tried that and 'python -m pip list -v' shows correctly but I get this error trying an install: Would that be related to my PATH at all? |
|
No idea, use |
|
Latest |
|
This seems to be working, thank you very much! :) |
|
👍 |
|
Thanks @benoit-pierre for helping out @legolego! :) |
|
@legolego It seems your issue is resolved, so I'll go ahead and close this issue. You can still comment on the closed to let us know if that is not the case -- I'll reopen this issue in that case. |
|
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. |
lock
bot
added
the
auto-locked
Environment
Pycharm IDE
Description
I'm having trouble installing modules with pip and venv. I had one environment working fine, but in PyCharm I made a second one to be 64 bit. I'm trying to reinstall my modules again, but not succeeding. They seem to install successfully and show up in 'pip list -v' but they're not actually there. This has less to do with pip and maybe more with venv and my PATH, but 'pip list -v' isn't showing correct data. Also, maybe more of a request, I don't see the actual destination directory used to install a module when using the --verbose flag. It would be a big hint to know exactly where the module is being installed.
Expected behavior
I would expect 'pip install' and 'pip list' to use the same location variable, maybe they're using different locations to install to and show modules internally.
How to Reproduce
pip list -v
Output
pip list -v output doesn't match what's in the Lib\site-packages directory.
The text was updated successfully, but these errors were encountered: