What does your pipenv workflow look like?

[danstewart]

With the recent changes surround --keep-outdated and the new upgrade command I'm looking into how we use pipenv and was wondering how other people do it.

The advice from the maintainers is to now pin dependency versions in the Pipfile and then everything just works but then upgrading things seems annoying.

Currently our workflow is to have everything unpinned in Pipfile (apart from things we know we want to keep at a specific version).

Installing dependencies for the first time

pipenv sync --dev

Installing new dependencies

# Install a new package without updating pipenv install --keep-outdated thing # or now that --keep-outdated is deprecated: pipenv upgrade thing

Removing dependencies

pipenv uninstall --keep-outdated thing

Updating dependencies (done every now and again to keep things up to date)

# Update everything that is not pinned, install, relock pipenv update

---

This all seems to work fine now, with the only issues being we still use --keep-outdated when removing packages.

Is this how others use pipenv?