Why pip install don't cache packages?

[hongyi-zhao]

Hi,

With the following environment:

$ pip --version
pip 20.0.2 from /home/werner/.pyenv/versions/3.8.1/envs/test1/lib/python3.8/site-packages/pip (python 3.8)

Tested with the following steps:

(test1) werner@ubuntu-01:~$ pip install six
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting six
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/65/eb/1f97cb97bfc2390a276969c6fae16075da282f5058082d4cb10c6c5c1dba/six-1.14.0-py2.py3-none-any.whl (10 kB)
Installing collected packages: six
Successfully installed six-1.14.0

(test1) werner@ubuntu-01:~$ pip uninstall six
Found existing installation: six 1.14.0
Uninstalling six-1.14.0:
  Would remove:
    /home/werner/.repo/github.com/pyenv/versions/linux-x86_64/3.8.1/envs/test1/lib/python3.8/site-packages/six-1.14.0.dist-info/*
    /home/werner/.repo/github.com/pyenv/versions/linux-x86_64/3.8.1/envs/test1/lib/python3.8/site-packages/six.py
Proceed (y/n)? y
  Successfully uninstalled six-1.14.0

(test1) werner@ubuntu-01:~$ pip install six
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting six
  Downloading https://pypi.tuna.tsinghua.edu.cn/packages/65/eb/1f97cb97bfc2390a276969c6fae16075da282f5058082d4cb10c6c5c1dba/six-1.14.0-py2.py3-none-any.whl (10 kB)
Installing collected packages: six
Successfully installed six-1.14.0

As you can see, when I run ``pip install'' for the second time, it will re-downloading the package instead of using the local cache.

And I also cannot find the downloaded package at the following location:

(test1) werner@ubuntu-01:~$ find ~/.cache/pip -type f -name 'six-1.14.0-py2.py3-none-any.whl'
(test1) werner@ubuntu-01:~$ 

Any hints?

Regards

[NoahGorny]

I suspect it has something to do with your index being insecure due to bad certs/old TLS.
Currently pip does not cache from insecure origins even if they are specified as "trusted hosts"

See #7847 and the PR I made to solve it #7885
Feel free to voice your opinion on the matter 😄

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[duckinator]

@pradyunsg can this be reopened? I've had the same problem and included the information that was asked for.

[pradyunsg]

Bot was looking for a response from someone else. :)

[moltar]

Uh, of course not. Cache happens in the container, and two different runs each starts from a fresh environment without cache, so they are the same. To actually compare the cached performance, you need to run pip install --force-reinstall twice in the same environment (I added a few -q to make the output more readable):

That's exactly what I did. I ran it in the same container.

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[pradyunsg]

Unlocked and relocked, to add back a cross-reference to the issue that contained sufficient context and whose author contributed a fix for this.