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

pipenv lock --clear doesn't clear the caches #2628

Closed
jakul opened this issue Jul 23, 2018 · 3 comments
Closed

pipenv lock --clear doesn't clear the caches #2628

jakul opened this issue Jul 23, 2018 · 3 comments

Comments

@jakul
Copy link

jakul commented Jul 23, 2018

Issue description

pipenv lock --clear doesn't clear the caches.

Steps to replicate
  1. Run pipenv lock --clear and look at the
$ pipenv lock --clear
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Updated Pipfile.lock (fabf2e)!
$ pipenv --version
pipenv, version 2018.7.1
Cause

The cause of this problem is that the clear logic only runs if ctx.invoked_subcommand is None. This means --clear won't work for most of the commands in the cli

@uranusjr
Copy link
Member

You’re reading the wrong code. pipenv lock --clear triggers a --clear option on lock, which is different from the global --clear.

@JBPressac
Copy link

Hello,
In this case, which is the "global" --clear ? pipenv --clear is not working (using pipenv 2018.11.26): ~/.cache/pipenv/ is not emptied.

Otherwise, could ~/.cache/pipenv/ content could be emptied manually ?
Thanks,

@astenuz
Copy link

astenuz commented May 20, 2020

Hi, I ended up in this issue while looking for ways to clear the packages cache. What is the global --clear? it does only seem to be available when using pipenv lock --clear

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants