-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 uninstall --keep-outdated
does not remove dev dependency from lockfile
#4263
Comments
Some other observations about differences:
|
I believe @techalchemy decided this is not a release blocker for the recent release. (Which is not to say it's not a bug -- just to reply on the question of whether it's a blocker.) |
Indeed, though it is a regression. |
Yes it should be! Between which versions did you see the changes? And more importantly, do they change between locks with the current release?
This is a big problem and one which requires some structural changes to the code I think.
Is the
I don't think a lot of thought went into the possibility of using I think this is an area that will need some attention. |
Filed #4278 to track separately. |
Thanks. I will start a PR at some point to work on the design issues with the |
To be clear: This command used to work in pipenv 2018.11.26 (at least insofar as it removed the requested dependency from the lockfile). So from my perspective, this is a regression, not a feature request. Can you elaborate on whether this regression was a side effect of some other intentional change? I think we discussed on IRC last night the possibility of using |
Confirmed that |
Any update here? I'm getting bit by a recent change to mypy because I can't use |
So I've resorted to removing the dependency from the lockfile using pipenv internals. Install
|
Is there any update on this? It's biting me right now. |
|
Possible blocker for #3369.
Pipfile:
With pipenv 2018.11.26:
With pipenv 2020.4.1b2:
The text was updated successfully, but these errors were encountered: