"pipenv uninstall --keep-outdated <package>" does not remove the removed package information in Pipfile.lock

Be sure to check the existing issues (both open and closed!), and make sure you are running the latest version of Pipenv.

Check the diagnose documentation for common issues before posting! We may close your issue if it is very similar to one of them. Please be considerate, or be on your way.

Make sure to mention your debugging experience if the documented solution failed.

Issue description

“pipenv uninstall --keep-outdated <package>” does not remove the removed package information in Pipfile.lock.

I often replace a package to the local one for debugging. In order to keep other dependencies, “–keep-outdated” is preferable as below.

 pipenv uninstall --keep-outdated <package>
 pipenv install --keep-outdated -e <local directory of package>

But actually these instructions fail to install <local directory of package> since Pipfile.lock keeps the package information by pipenv uninstall --keep-outdated <package> and pipenv install --keep-outdated -e <local directory of package> installs <package> instead of <local directory of package>.

Expected result

“pipenv uninstall --keep-outdated <package>” removes the removed package information in Pipfile.lock.

Actual result

When possible, provide the verbose output (--verbose), especially for locking and dependencies resolving issues.

Steps to replicate

pipenv install urllib3
pipenv uninstall --keep-outdated urllib3

---

Please run $ pipenv --support, and paste the results here. Don’t put backticks (`) around it! The output already contains Markdown formatting.

I tried to paste it but hesitated it because it exposes many private environmental variables. Please improve this instruction.

[jkogler-cloudflight]

@tisdall The _meta hash is only computed with the data in the Pipfile. So if you manually change something in the Pipfile.lock, it will not change. So everything good.

[matteius]

Verified on master.