Menu
According to pipenv official documentation:
sync
pipenv sync [OPTIONS]
Installs all packages specified in Pipfile.lock.
install
pipenv install [OPTIONS] [PACKAGES]...
Installs provided packages and adds them to Pipfile, or (if no packages are given), installs all packages from Pipfile.
--ignore-pipfile Ignore Pipfile when installing, using the Pipfile.lock.
Is it safe to assume pipenv sync and pipenv install --ignore-pipfile are identical without any hidden drawbacks?
More background: I was using --system flag to install the python packages to the system since I don't care about isolated environments in a docker container. However --system flag is unavailable for pipenv sync (See github issue), so I figured pipenv install --system --ignore-pipfile might be a viable hack.
469
$ pipenv lock is used to create a Pipfile. lock , which declares all dependencies (and sub-dependencies) of your project, their latest available versions, and the current hashes for the downloaded files.
You might also want to add --ignore-pipfile to pipenv install , as to not accidentally modify the lock-file on each test run. This causes Pipenv to ignore changes to the Pipfile and (more importantly) prevents it from adding the current environment to Pipfile.
pipenv sync will install the exact versions specified in Pipfile. lock. I would say sync is better for getting your environment to match what is checked in, and install is for when you want to get the latest versions, or are adding new dependencies that aren't in the lock file yet.
That file is impossible for human to deal with, you can only deal with Pipfile . But Pipfile is not strict enough to reproduce a totally same environment. So that's why we also need a Pipfile. lock .
you can see the notes in Advanced usage of pipenv
pipenv install --ignore-pipfileis nearly equivalent topipenv sync, butpipenv syncwill never attempt to re-lock your dependencies as it is considered an atomic operation.pipenv installby default does attempt to re-lock unless using the--deployflag.
so maybe pipenv install --ignore-pipfile --deploy equal to pipenv sync
188
Not really an answer (I'd be interested in confirmation as well) but for what it's worth, we've been using
pipenv install --system --deploy --ignore-pipfile
in our Dockerfile with good results.
28
Not sure whether it was added after you posted this question, but the documentation does address this very question (although, to be fair, it's kinda of a "uh?" type of explanation for me...)
FWIW, I believe that sync should have the --system flag too (I'm trying to address the very same issue as you, of building a container, and do not want to maintain two separate files: requirements.txt for the container's system Python, and Pipfile for my dev virtual env).
Your "hack" seems to me currently the only viable option.
33
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
