Pipfile.lock getting clobbered with path based dependencies

[greenape]

We have a a couple of Pipfiles which have another path in the same repo as an editable dependency, e.g. project_b = {editable = true,path = "./../project_b"} in project a's Pipfile.

When dependabot updates the lock file for project a, the lock files lose all the previously locked deps from project b (e.g. Flowminder/FlowKit@7ff5d33), necessitating a manual relock of the Pipfile.

Anything we can do to stop that happening?

[greysteil]

Oooh, that looks like a bug to me. Let me dig into it.

[greysteil]

Ack, actually, on second thoughts, I think what's needed here is this feature in Pipenv, which should be released soon. 🤞

[greenape]

I did wonder if that might be the issue actually. Pipenv’s release cycle could do with being bit more frequent 🙄

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within seven days. Thank you for your contributions.

[greenape]

Any chance this is going to be resolved now there's a new Pipenv release?