Idea: Detect out-of-date environment in ”shell” and “run”

Was working on Pipenv and got an ImportError when I do pipenv run .... Took me a minute to realise “oh yeah there’s a new dependency, I need to pipenv sync”.

It would be pretty neat if Pipenv can tell me something like

$ pipenv run ...
Notice: Your environment is out of sync to Pipfile.lock. Run pipenv sync or pipenv sync --dev to update!
[Attempt to run the script anyway]

I’m not sure if this is even feasible, but it would be a very-nice-to-have.

[ncoghlan]

Something that we could potentially do to make this a relatively fast check is to add a metadata file inside the venv directory that captures the lock file hash (which would thus go stale when git pull replaced your lock file).

I’d still be wary of adding that check to pipenv run for startup latency reasons, but that concern could be handled via a --skip-sync-check flag.

[uranusjr]

It still could take a while though. Maybe it’s a good idea to implement it as an opt-in, but that would make it a low-priority feature. I’m open to contributions if anyone is interested, however.