-
-
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
Uninstall of python-dotenv does not (really) work #5652
Comments
@soraphis Ok I spent a bit debugging this, and it seems it is because you have |
Sorry, I was slightly off base in my last response, the real reason its included is |
Thanks for taking the time and looking into it. What I don't really get is: why isn't showing up in the graph? Other dependencies are also listed multiple times if required by multiple packages... |
For the record, I tested this the other day out of curiosity. PDM also installs |
The new version of pipdeptree appears to fix this, I have a PR out to update pipenv.
|
Well it kind of fixes it -- it shows up in the graph, just not under uvicorn, which seems odd. |
Whether it appears in the graph is kind of secondary, I think. The real problem here is that:
Thus:
IIRC, Pure speculation: maybe the resolver includes all optional dependencies, thus |
Actually that part is easy to explain @derula --
|
Ah, okay, I must have missed that. Then I guess there are 2 separate problems:
|
@derula that should be reported upstream to |
Upstream ticket has existed for over 4 years: tox-dev/pipdeptree/issues/107 |
Issue description
I also tried reaching out on stackoverflow, but at this point. it feels like a bug
version: pipenv, version 2023.3.20
I try to uninstall python-dotenv. Should be easy, right? It's not in my Pipfile, and in my pipenv-graph it's not listed as a transitive dependency.
Following this series of commands:
notice, how it's NOT deleted from the Pipfile.lock?, well, if i now run "pipenv install", I went full circle and have it back in my pipenv graph.
I thought removing it manually from the pipfile lock would work, but after running "pipenv lock" (or any other command that recreates the lockfile) it's back in there again, even if it was not present in the Pipfile nor pipenv graph.
Expected result
the package being actually removed, and not reappearing again
pipenv --support is way to large to paste here
pipenv__support.txt
The text was updated successfully, but these errors were encountered: