3 ms·
I think you are supposed to use `pipenv sync` on the remote to get the pinned versions from the lock file
by sethgecko 8y ago
I think you are supposed to use `pipenv sync` on the remote to get the pinned versions from the lock file
- ben509 8y agoThat's honestly my biggest gripe with pipenv: which command is best for a CI run? My current magic is: pipenv sync $(pipenv --venv > /dev/null || echo '--python 3.6') --dev The reason is that (magically) adding --python 3.6 will always create a new virtual environment, and I'd rather not do that if the cache is up to date, but running sync by itself won't. And I think I also want to run `install --deploy`, to check if my Pipfile / lock are in sync or broken. None of them are huge gripes, more the frustration that it almost works out of the box, but it always seems no one writing these tools ever uses them in prod...
- luhn 8y agoI use `pipenv install --deploy --system`. Doesn't create a virtualenv and verifies the lock file. Of course, I definitely understand where you're coming from. It took quite a while for me to figure that out, because --deploy is not well documented.
- ben509 8y agoI'm not sure I want to use --system in CI, just to avoid differences with development machines if possible. That does simplify baking a Docker image, though.