Cannot do: pipenv uninstall --skip-lock despite documentation #2848
Comments
Hmmm that is an interesting suggestion. It seems straightforward — if it’s present in your pipfile, we can remove it, if not, it will just be removed from the lockfile. This makes sense to me simply as an interface over your pipfile from a UX standpoint. However locking should also benefit from speedups we added a long time ago related to caching, so there may be more going on here |
As of 2018.10.13,
|
techalchemy
added a commit
that referenced
this issue
Nov 3, 2018
- Fixes #2848 Signed-off-by: Dan Ryan <dan@danryan.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
Using the
--skip-lock
flag withpipenv uninstall
results in :Although the documentation states that:
(therefore including --skip-lock)
Obviously, this can be a simple documentation fix, but it would be more interesting to add the
skip-lock
flag topipenv uninstall
. This is interesting for CI environments, where you might want to drop a package temporarily and don't care about locking the dependencies (that takes a significant amount of times, > 7 mins in my env). In one word: speedup.The text was updated successfully, but these errors were encountered: