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

pip running under Python2 and then Python3 can't read cache #5308

Closed
aabdnn opened this issue Apr 20, 2018 · 4 comments
Closed

pip running under Python2 and then Python3 can't read cache #5308

aabdnn opened this issue Apr 20, 2018 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@aabdnn
Copy link

aabdnn commented Apr 20, 2018

  • Pip version: 10.0.1
  • Python version: 2.7.10, 3.6.3
  • Operating system: MacOSX

Description:

After upgrading to pip 10.0.1, whenever I run pip under different Python versions, there are problems reading the cache.

What I've run:

~% rm -rf ~/Library/Caches/pip
~% pip -V
pip 10.0.1 from /usr/local/venv/py2main/lib/python2.7/site-packages/pip (python 2.7)
~% pip list -o
~% pip3 -V
pip 10.0.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)
~% pip3 list -o
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
Cache entry deserialization failed, entry ignored
@StephanErb
Copy link
Contributor

Maybe this is a regression of psf/cachecontrol#146?

@pradyunsg
Copy link
Member

We are on a version of cachecontrol that has that patch.

CacheControl==0.12.4

Pinging @dstufft on this.

@pradyunsg pradyunsg added the S: needs triage Issues/PRs that need to be triaged label May 10, 2018
@pradyunsg
Copy link
Member

Maybe this is a regression of psf/cachecontrol#146?

Yep. It didn't sanitize the headers.


Closing this issue as a duplicate of #5250.

@pradyunsg pradyunsg removed the S: needs triage Issues/PRs that need to be triaged label Jun 5, 2018
@lock
Copy link

lock bot commented Jun 2, 2019

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 lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 2, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

3 participants