Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

About

Workflows with python’s new development/packaging environment tool.

Guidelines

Pipenv handles converting setup.py’s abstract dependencies into concrete dependencies and driving a virtual environment with them.

Files

  • Abstract dependency rules are in ./Pipfile

  • Concrete dependency versions are locked in ./Pipfile.lock

  • Virtualenvs are created in ~/.local/share/virtualenvs.

Workflow

> pipenv --three
> pipenv install pydot             (rule for a specific dependency)
> pipenv install --dev -e .        (rules for everything in extras_requires?)
> pipenv install --dev -e .[docs]  (rules for everything in extras_requires specified by keywords)
> pipenv install -e .              (rules for everything in install_requires)
> pipenv install --dev             (install every development dependency into the virtualenv)
> pipenv install                   (install every install dependency into the virtualenv)
> pipenv update                    (equilavent to pipenv lock && pipenv sync)

  • No labels