a way to tell that the virtualenv and Pipfile.lock are in sync?

Ran the following

pipenv run ...
Creating a virtualenv for this project…
Using /usr/bin/python2.7 to create virtualenv…
⠋Running virtualenv with interpreter /usr/bin/python2.7
New python executable in /home/user/.virtualenvs/...-RVyaMy2x/bin/python2.7
Also creating executable in /home/user/.virtualenvs/...-RVyaMy2x/bin/python
Installing setuptools, pip, wheel...done.
...
ImportError: No module named yaml

Describe your environment

1. Ubuntu 16.04
2. Python 2.7.12
3. pipenv, version 8.3.2

Expected result

Expected one of the following:

1. Automatically install dependencies when pipenv run ... is called and all dependencies aren’t in the virtualenv
2. Add optional flag to do 1
3. Add command to test if dependencies are installed so that I can run pipenv install before running pipenv run ... (as it stands now, pipenv install is fairly time consuming so I don’t want to run it unconditionally)
4. Modify pipenv check to check if all dependencies are installed and correct

I can try to make this change, just wanted to make sure it’s something that you’d be okay merging.

Actual result

Virtualenv was installed but packages were not.

Steps to replicate

Run pipenv run ... on a python file with Pipfile.lock present, without running pipenv install first.

[kennethreitz]

i don’t care what your expectation is, i’m closing it. thank you — it has been noted, as i said 😃

[nfisher]

It would be super useful for speeding up CI builds if sync had a flag to exit if everything is in sync. A lot of SaaS CI platforms include code caches such as Travis, AWS codebuild, Bitbucket Pipelines, etc. The code cache is restored at the beginning of a run and if the dependencies didn’t require updates it could shave 30s or more off of the build.

As it is pipenv sync --dev takes about 30s with a private build. It contains 100 or so deps in total. If pipenv verify (or whatever) had a return code of 1 on “out of sync” and 0 when it’s “in sync”.

Basically it would allow me to write something like this;

pipenv verify --dev
if [ $? -eq 1 ]; then
pipenv sync --dev
fi

If pipenv did the above internally that would be even better!

I will look at doing a diff between pipenv lock -r and pip freeze in the interim.