Updating specific requirements is something I need to do pretty often, and it's not fun to explain all the Pipenv quirks to the team.
Pip-tools looks like it does everything I need and has fewer quirks, so I ended up making the switch.
Pipenv uses pip-tools under the hood, so the migration to pip-tools was very smooth. The migration process was:
- Copy the dev-packages and packages sections of the Pipfile to their own requirements.in files.
- Run pip-compile
- Copy over the specific versions and hashes from the Pipfile.lock to the generated requirements.txt.