| Name | pipenv JSON |
| Version |
2023.12.1
JSON |
| download |
| home_page | |
| Summary | Python Development Workflow for Humans. |
| upload_time | 2024-02-05 01:04:09 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.8 |
| license | The MIT License (MIT) Copyright 2020-2022 Python Packaging Authority Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
Pipenv: Python Development Workflow for Humans
==============================================
[](https://python.org/pypi/pipenv)
[](https://python.org/pypi/pipenv)
[](https://github.com/pypa/pipenv/actions/workflows/ci.yaml)
[](https://python.org/pypi/pipenv)
------------------------------------------------------------------------
**Pipenv** is a Python virtualenv management tool that supports a multitude of systems and nicely bridges the gaps between pip, python (using system python, pyenv or asdf) and virtualenv.
*Linux, macOS, and Windows are all first-class citizens in pipenv.*
Pipenv automatically creates and manages a virtualenv for your projects, as well as adds/removes packages from your `Pipfile` as you install/uninstall packages. It also generates a project `Pipfile.lock`, which is used to produce deterministic builds.
Pipenv is primarily meant to provide users and developers of applications with an easy method to arrive at a consistent working project environment.
The problems that Pipenv seeks to solve are multi-faceted:
- You no longer need to use `pip` and `virtualenv` separately: they work together.
- Managing a `requirements.txt` file with package hashes can be problematic. Pipenv uses `Pipfile` and `Pipfile.lock` to separate abstract dependency declarations from the last tested combination.
- Hashes are documented in the lock file which are verified during install. Security considerations are put first.
- Strongly encourage the use of the latest versions of dependencies to minimize security risks [arising from outdated components](https://www.owasp.org/index.php/Top_10-2017_A9-Using_Components_with_Known_Vulnerabilities).
- Gives you insight into your dependency graph (e.g. `$ pipenv graph`).
- Streamline development workflow by supporting local customizations with `.env` files.
Table Of Contents
------------------
- [Pipenv](#pipenv-python-development-workflow-for-humans)
- [Installation](#installation)
- [Features](#features)
- [Basic Concepts](#basic-concepts)
- [Other Commands](#other-commands)
- [Shell Completion](#shell-completion)
- [Usage](#usage)
- [Usage Examples](#usage-examples)
- [Commands](#commands)
- [Locate the Project](#locate-the-project)
- [Locate the virtualenv](#locate-the-virtualenv)
- [Locate the Python Interpreter](#locate-the-python-interpreter)
- [Install Packages](#install-packages)
- [Installing from git](#installing-from-git)
- [Install a dev dependency](#install-a-dev-dependency)
- [Show a dependency graph](#show-a-dependency-graph)
- [Generate a lockfile](#generate-a-lockfile)
- [Install all dev dependencies](#install-all-dev-dependencies)
- [Uninstall everything](#uninstall-everything)
- [Use the shell](#use-the-shell)
- [Documentation](#documentation)
Installation
------------
**Pipenv can be installed with Python 3.7 and above.**
For most users, we recommend installing Pipenv using `pip`:
pip install --user pipenv
Or, if you\'re using Fedora:
sudo dnf install pipenv
Or, if you\'re using FreeBSD:
pkg install py39-pipenv
Or, if you\'re using Gentoo:
sudo emerge pipenv
Or, if you\'re using Void Linux:
sudo xbps-install -S python3-pipenv
Alternatively, some users prefer to use [Pipx](https://pypi.org/p/pipx):
pipx install pipenv
Or, some users prefer to use Python pip module
python -m pip install pipenv
Refer to the [documentation](https://pipenv.pypa.io/en/latest/#install-pipenv-today) for latest instructions.
✨🍰✨
Features
----------
- Enables truly *deterministic builds*, while easily specifying *only
what you want*.
- Generates and checks file hashes for locked dependencies.
- Automatically install required Pythons, if `pyenv` or `asdf` is available.
- Automatically finds your project home, recursively, by looking for a
`Pipfile`.
- Automatically generates a `Pipfile`, if one doesn\'t exist.
- Automatically creates a virtualenv in a standard location.
- Automatically adds/removes packages to a `Pipfile` when they are installed/uninstalled.
- Automatically loads `.env` files, if they exist.
For command reference, see [Commands](https://pipenv.pypa.io/en/latest/commands/).
### Basic Concepts
- A virtualenv will automatically be created, when one doesn\'t exist.
- When no parameters are passed to `install`, all packages
`[packages]` specified will be installed.
- Otherwise, whatever virtualenv defaults to will be the default.
### Shell Completion
To enable completion in fish, add this to your configuration `~/.config/fish/completions/pipenv.fish`:
eval (env _PIPENV_COMPLETE=fish_source pipenv)
There is also a [fish plugin](https://github.com/fisherman/pipenv), which will automatically
activate your subshells for you!
Alternatively, with zsh, add this to your configuration `~/.zshrc`:
eval "$(_PIPENV_COMPLETE=zsh_source pipenv)"
Alternatively, with bash, add this to your configuration `~/.bashrc` or `~/.bash_profile`:
eval "$(_PIPENV_COMPLETE=bash_source pipenv)"
Magic shell completions are now enabled!
Usage
-------
$ pipenv --help
Usage: pipenv [OPTIONS] COMMAND [ARGS]...
Options:
--where Output project home information.
--venv Output virtualenv information.
--py Output Python interpreter information.
--envs Output Environment Variable options.
--rm Remove the virtualenv.
--bare Minimal output.
--man Display manpage.
--support Output diagnostic information for use in
GitHub issues.
--site-packages / --no-site-packages
Enable site-packages for the virtualenv.
[env var: PIPENV_SITE_PACKAGES]
--python TEXT Specify which version of Python virtualenv
should use.
--clear Clears caches (pipenv, pip). [env var:
PIPENV_CLEAR]
-q, --quiet Quiet mode.
-v, --verbose Verbose mode.
--pypi-mirror TEXT Specify a PyPI mirror.
--version Show the version and exit.
-h, --help Show this message and exit.
### Usage Examples:
Create a new project using Python 3.7, specifically:
$ pipenv --python 3.7
Remove project virtualenv (inferred from current directory):
$ pipenv --rm
Install all dependencies for a project (including dev):
$ pipenv install --dev
Create a lockfile containing pre-releases:
$ pipenv lock --pre
Show a graph of your installed dependencies:
$ pipenv graph
Check your installed dependencies for security vulnerabilities:
$ pipenv check
Install a local setup.py into your virtual environment/Pipfile:
$ pipenv install -e .
Use a lower-level pip command:
$ pipenv run pip freeze
### Commands:
check Checks for PyUp Safety security vulnerabilities and against
PEP 508 markers provided in Pipfile.
clean Uninstalls all packages not specified in Pipfile.lock.
graph Displays currently-installed dependency graph information.
install Installs provided packages and adds them to Pipfile, or (if no
packages are given), installs all packages from Pipfile.
lock Generates Pipfile.lock.
open View a given module in your editor.
requirements Generate a requirements.txt from Pipfile.lock.
run Spawns a command installed into the virtualenv.
scripts Lists scripts in current environment config.
shell Spawns a shell within the virtualenv.
sync Installs all packages specified in Pipfile.lock.
uninstall Uninstalls a provided package and removes it from Pipfile.
update Runs lock, then sync.
upgrade Update the lock of the specified dependency / sub-dependency,
but does not actually install the packages.
verify Verify the hash in Pipfile.lock is up-to-date.
### Locate the project:
$ pipenv --where
/Users/kennethreitz/Library/Mobile Documents/com~apple~CloudDocs/repos/kr/pipenv/test
### Locate the virtualenv:
$ pipenv --venv
/Users/kennethreitz/.local/share/virtualenvs/test-Skyy4vre
### Locate the Python interpreter:
$ pipenv --py
/Users/kennethreitz/.local/share/virtualenvs/test-Skyy4vre/bin/python
### Install packages:
$ pipenv install
Creating a virtualenv for this project...
...
No package provided, installing all dependencies.
Virtualenv location: /Users/kennethreitz/.local/share/virtualenvs/test-EJkjoYts
Installing dependencies from Pipfile.lock...
...
To activate this project's virtualenv, run the following:
$ pipenv shell
### Installing from git:
You can install packages with pipenv from git and other version control systems using URLs formatted according to the following rule:
<vcs_type>+<scheme>://<location>/<user_or_organization>/<repository>@<branch_or_tag>#<package_name>
The only optional section is the `@<branch_or_tag>` section. When using git over SSH, you may use the shorthand vcs and scheme alias `git+git@<location>:<user_or_organization>/<repository>@<branch_or_tag>#<package_name>`. Note that this is translated to `git+ssh://git@<location>` when parsed.
Valid values for `<vcs_type>` include `git`, `bzr`, `svn`, and `hg`. Valid values for `<scheme>` include `http,`, `https`, `ssh`, and `file`. In specific cases you also have access to other schemes: `svn` may be combined with `svn` as a scheme, and `bzr` can be combined with `sftp` and `lp`.
Note that it is **strongly recommended** that you install any version-controlled dependencies in editable mode, using `pipenv install -e`, in order to ensure that dependency resolution can be performed with an up to date copy of the repository each time it is performed, and that it includes all known dependencies.
Below is an example usage which installs the git repository located at `https://github.com/requests/requests.git` from tag `v2.19.1` as package name `requests`:
$ pipenv install -e git+https://github.com/requests/requests.git@v2.19#egg=requests
Creating a Pipfile for this project...
Installing -e git+https://github.com/requests/requests.git@v2.19.1#egg=requests...
[...snipped...]
Adding -e git+https://github.com/requests/requests.git@v2.19.1#egg=requests to Pipfile's [packages]...
[...]
You can read more about [pip's implementation of vcs support here](https://pip.pypa.io/en/stable/topics/vcs-support/).
### Install a dev dependency:
$ pipenv install pytest --dev
Installing pytest...
...
Adding pytest to Pipfile's [dev-packages]...
### Show a dependency graph:
$ pipenv graph
requests==2.18.4
- certifi [required: >=2017.4.17, installed: 2017.7.27.1]
- chardet [required: >=3.0.2,<3.1.0, installed: 3.0.4]
- idna [required: >=2.5,<2.7, installed: 2.6]
- urllib3 [required: <1.23,>=1.21.1, installed: 1.22]
### Generate a lockfile:
$ pipenv lock
Assuring all dependencies from Pipfile are installed...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Note: your project now has only default [packages] installed.
To install [dev-packages], run: $ pipenv install --dev
### Install all dev dependencies:
$ pipenv install --dev
Pipfile found at /Users/kennethreitz/repos/kr/pip2/test/Pipfile. Considering this to be the project home.
Pipfile.lock out of date, updating...
Assuring all dependencies from Pipfile are installed...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
### Uninstall everything:
$ pipenv uninstall --all
No package provided, un-installing all dependencies.
Found 25 installed package(s), purging...
...
Environment now purged and fresh!
### Use the shell:
$ pipenv shell
Loading .env environment variables...
Launching subshell in virtual environment. Type 'exit' or 'Ctrl+D' to return.
$ ▯
### PURPOSE AND ADVANTAGES OF PIPENV
To understand the problems that Pipenv solves, it's useful to show how Python package management has evolved.
Take yourself back to the first Python iteration. We had Python, but there was no clean way to install packages.
Then came Easy Install, a package that installs other Python packages with relative ease. But it came with a catch: it wasn't easy to uninstall packages that were no longer needed.
Enter pip, which most Python users are familiar with. pip lets us install and uninstall packages. We could specify versions, run pip freeze > requirements.txt to output a list of installed packages to a text file, and use that same text file to install everything an app needed with pip install -r requirements.txt.
But pip didn't include a way to isolate packages from each other. We might work on apps that use different versions of the same libraries, so we needed a way to enable that.
Pipenv aims to solve several problems.
First, the problem of needing the pip library for package installation, plus a library for creating a virtual environment, plus a library for managing virtual environments, plus all the commands associated with those libraries. That's a lot to manage. Pipenv ships with package management and virtual environment support, so you can use one tool to install, uninstall, track, and document your dependencies and to create, use, and organize your virtual environments. When you start a project with it, Pipenv will automatically create a virtual environment for that project if you aren't already using one.
Pipenv accomplishes this dependency management by abandoning the requirements.txt norm and trading it for a new document called a Pipfile. When you install a library with Pipenv, a Pipfile for your project is automatically updated with the details of that installation, including version information and possibly the Git repository location, file path, and other information.
Second, Pipenv wants to make it easier to manage complex interdependencies.
Using Pipenv, which gives you Pipfile, lets you avoid these problems by managing dependencies for different environments for you. This command will install the main project dependencies:
pipenv install
Adding the --dev tag will install the dev/testing requirements:
pipenv install --dev
To generate a Pipfile.lock file, run:
pipenv lock
You can also run Python scripts with Pipenv. To run a top-level Python script called hello.py, run:
pipenv run python hello.py
And you will see your expected result in the console.
To start a shell, run:
pipenv shell
If you would like to convert a project that currently uses a requirements.txt file to use Pipenv, install Pipenv and run:
pipenv install requirements.txt
This will create a Pipfile and install the specified requirements.
Documentation
---------------
Documentation resides over at [pipenv.pypa.io](https://pipenv.pypa.io/en/latest/).
## Star History
<a href="https://star-history.com/#pypa/pipenv&Date">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=pypa/pipenv&type=Date&theme=dark" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=pypa/pipenv&type=Date" />
<img alt="Star History Chart" src="https://api.star-history.com/svg?repos=pypa/pipenv&type=Date" />
</picture>
</a>
Raw data
{
"_id": null,
"home_page": "",
"name": "pipenv",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "",
"keywords": "",
"author": "",
"author_email": "Pipenv maintainer team <distutils-sig@python.org>",
"download_url": "https://files.pythonhosted.org/packages/a6/26/5cdf9f0c6eb835074c3e43dde2880bfa739daa23fa534a5dd65848af5913/pipenv-2023.12.1.tar.gz",
"platform": null,
"description": "Pipenv: Python Development Workflow for Humans\n==============================================\n\n[](https://python.org/pypi/pipenv)\n[](https://python.org/pypi/pipenv)\n[](https://github.com/pypa/pipenv/actions/workflows/ci.yaml)\n[](https://python.org/pypi/pipenv)\n\n------------------------------------------------------------------------\n\n**Pipenv** is a Python virtualenv management tool that supports a multitude of systems and nicely bridges the gaps between pip, python (using system python, pyenv or asdf) and virtualenv.\n*Linux, macOS, and Windows are all first-class citizens in pipenv.*\n\nPipenv automatically creates and manages a virtualenv for your projects, as well as adds/removes packages from your `Pipfile` as you install/uninstall packages. It also generates a project `Pipfile.lock`, which is used to produce deterministic builds.\n\nPipenv is primarily meant to provide users and developers of applications with an easy method to arrive at a consistent working project environment.\n\nThe problems that Pipenv seeks to solve are multi-faceted:\n\n- You no longer need to use `pip` and `virtualenv` separately: they work together.\n- Managing a `requirements.txt` file with package hashes can be problematic. Pipenv uses `Pipfile` and `Pipfile.lock` to separate abstract dependency declarations from the last tested combination.\n- Hashes are documented in the lock file which are verified during install. Security considerations are put first.\n- Strongly encourage the use of the latest versions of dependencies to minimize security risks [arising from outdated components](https://www.owasp.org/index.php/Top_10-2017_A9-Using_Components_with_Known_Vulnerabilities).\n- Gives you insight into your dependency graph (e.g. `$ pipenv graph`).\n- Streamline development workflow by supporting local customizations with `.env` files.\n\nTable Of Contents\n------------------\n\n- [Pipenv](#pipenv-python-development-workflow-for-humans)\n\n- [Installation](#installation)\n\n- [Features](#features)\n\n- [Basic Concepts](#basic-concepts)\n\n- [Other Commands](#other-commands)\n\n- [Shell Completion](#shell-completion)\n\n- [Usage](#usage)\n\n - [Usage Examples](#usage-examples)\n\n - [Commands](#commands)\n\n - [Locate the Project](#locate-the-project)\n\n - [Locate the virtualenv](#locate-the-virtualenv)\n\n - [Locate the Python Interpreter](#locate-the-python-interpreter)\n\n - [Install Packages](#install-packages)\n\n - [Installing from git](#installing-from-git)\n\n - [Install a dev dependency](#install-a-dev-dependency)\n\n - [Show a dependency graph](#show-a-dependency-graph)\n\n - [Generate a lockfile](#generate-a-lockfile)\n\n - [Install all dev dependencies](#install-all-dev-dependencies)\n\n - [Uninstall everything](#uninstall-everything)\n\n - [Use the shell](#use-the-shell)\n\n- [Documentation](#documentation)\n\nInstallation\n------------\n\n**Pipenv can be installed with Python 3.7 and above.**\n\nFor most users, we recommend installing Pipenv using `pip`:\n\n pip install --user pipenv\n\nOr, if you\\'re using Fedora:\n\n sudo dnf install pipenv\n\nOr, if you\\'re using FreeBSD:\n\n pkg install py39-pipenv\n\nOr, if you\\'re using Gentoo:\n\n sudo emerge pipenv\n\nOr, if you\\'re using Void Linux:\n\n sudo xbps-install -S python3-pipenv\n\nAlternatively, some users prefer to use [Pipx](https://pypi.org/p/pipx):\n\n pipx install pipenv\n\nOr, some users prefer to use Python pip module\n\n python -m pip install pipenv\n\nRefer to the [documentation](https://pipenv.pypa.io/en/latest/#install-pipenv-today) for latest instructions.\n\n\u2728\ud83c\udf70\u2728\n\nFeatures\n----------\n\n- Enables truly *deterministic builds*, while easily specifying *only\n what you want*.\n- Generates and checks file hashes for locked dependencies.\n- Automatically install required Pythons, if `pyenv` or `asdf` is available.\n- Automatically finds your project home, recursively, by looking for a\n `Pipfile`.\n- Automatically generates a `Pipfile`, if one doesn\\'t exist.\n- Automatically creates a virtualenv in a standard location.\n- Automatically adds/removes packages to a `Pipfile` when they are installed/uninstalled.\n- Automatically loads `.env` files, if they exist.\n\nFor command reference, see [Commands](https://pipenv.pypa.io/en/latest/commands/).\n\n### Basic Concepts\n\n- A virtualenv will automatically be created, when one doesn\\'t exist.\n- When no parameters are passed to `install`, all packages\n `[packages]` specified will be installed.\n- Otherwise, whatever virtualenv defaults to will be the default.\n\n\n### Shell Completion\n\nTo enable completion in fish, add this to your configuration `~/.config/fish/completions/pipenv.fish`:\n\n eval (env _PIPENV_COMPLETE=fish_source pipenv)\n\nThere is also a [fish plugin](https://github.com/fisherman/pipenv), which will automatically\nactivate your subshells for you!\n\nAlternatively, with zsh, add this to your configuration `~/.zshrc`:\n\n eval \"$(_PIPENV_COMPLETE=zsh_source pipenv)\"\n\nAlternatively, with bash, add this to your configuration `~/.bashrc` or `~/.bash_profile`:\n\n eval \"$(_PIPENV_COMPLETE=bash_source pipenv)\"\n\nMagic shell completions are now enabled!\n\nUsage\n-------\n\n $ pipenv --help\n Usage: pipenv [OPTIONS] COMMAND [ARGS]...\n\n Options:\n --where Output project home information.\n --venv Output virtualenv information.\n --py Output Python interpreter information.\n --envs Output Environment Variable options.\n --rm Remove the virtualenv.\n --bare Minimal output.\n --man Display manpage.\n --support Output diagnostic information for use in\n GitHub issues.\n --site-packages / --no-site-packages\n Enable site-packages for the virtualenv.\n [env var: PIPENV_SITE_PACKAGES]\n --python TEXT Specify which version of Python virtualenv\n should use.\n --clear Clears caches (pipenv, pip). [env var:\n PIPENV_CLEAR]\n -q, --quiet Quiet mode.\n -v, --verbose Verbose mode.\n --pypi-mirror TEXT Specify a PyPI mirror.\n --version Show the version and exit.\n -h, --help Show this message and exit.\n\n\n ### Usage Examples:\n\n Create a new project using Python 3.7, specifically:\n $ pipenv --python 3.7\n\n Remove project virtualenv (inferred from current directory):\n $ pipenv --rm\n\n Install all dependencies for a project (including dev):\n $ pipenv install --dev\n\n Create a lockfile containing pre-releases:\n $ pipenv lock --pre\n\n Show a graph of your installed dependencies:\n $ pipenv graph\n\n Check your installed dependencies for security vulnerabilities:\n $ pipenv check\n\n Install a local setup.py into your virtual environment/Pipfile:\n $ pipenv install -e .\n\n Use a lower-level pip command:\n $ pipenv run pip freeze\n\n ### Commands:\n\n check Checks for PyUp Safety security vulnerabilities and against\n PEP 508 markers provided in Pipfile.\n clean Uninstalls all packages not specified in Pipfile.lock.\n graph Displays currently-installed dependency graph information.\n install Installs provided packages and adds them to Pipfile, or (if no\n packages are given), installs all packages from Pipfile.\n lock Generates Pipfile.lock.\n open View a given module in your editor.\n requirements Generate a requirements.txt from Pipfile.lock.\n run Spawns a command installed into the virtualenv.\n scripts Lists scripts in current environment config.\n shell Spawns a shell within the virtualenv.\n sync Installs all packages specified in Pipfile.lock.\n uninstall Uninstalls a provided package and removes it from Pipfile.\n update Runs lock, then sync.\n upgrade Update the lock of the specified dependency / sub-dependency,\n but does not actually install the packages.\n verify Verify the hash in Pipfile.lock is up-to-date.\n\n\n### Locate the project:\n\n $ pipenv --where\n /Users/kennethreitz/Library/Mobile Documents/com~apple~CloudDocs/repos/kr/pipenv/test\n\n### Locate the virtualenv:\n\n $ pipenv --venv\n /Users/kennethreitz/.local/share/virtualenvs/test-Skyy4vre\n\n### Locate the Python interpreter:\n\n $ pipenv --py\n /Users/kennethreitz/.local/share/virtualenvs/test-Skyy4vre/bin/python\n\n### Install packages:\n\n $ pipenv install\n Creating a virtualenv for this project...\n ...\n No package provided, installing all dependencies.\n Virtualenv location: /Users/kennethreitz/.local/share/virtualenvs/test-EJkjoYts\n Installing dependencies from Pipfile.lock...\n ...\n\n To activate this project's virtualenv, run the following:\n $ pipenv shell\n\n### Installing from git:\n\nYou can install packages with pipenv from git and other version control systems using URLs formatted according to the following rule:\n\n <vcs_type>+<scheme>://<location>/<user_or_organization>/<repository>@<branch_or_tag>#<package_name>\n\nThe only optional section is the `@<branch_or_tag>` section. When using git over SSH, you may use the shorthand vcs and scheme alias `git+git@<location>:<user_or_organization>/<repository>@<branch_or_tag>#<package_name>`. Note that this is translated to `git+ssh://git@<location>` when parsed.\n\nValid values for `<vcs_type>` include `git`, `bzr`, `svn`, and `hg`. Valid values for `<scheme>` include `http,`, `https`, `ssh`, and `file`. In specific cases you also have access to other schemes: `svn` may be combined with `svn` as a scheme, and `bzr` can be combined with `sftp` and `lp`.\n\nNote that it is **strongly recommended** that you install any version-controlled dependencies in editable mode, using `pipenv install -e`, in order to ensure that dependency resolution can be performed with an up to date copy of the repository each time it is performed, and that it includes all known dependencies.\n\nBelow is an example usage which installs the git repository located at `https://github.com/requests/requests.git` from tag `v2.19.1` as package name `requests`:\n\n $ pipenv install -e git+https://github.com/requests/requests.git@v2.19#egg=requests\n Creating a Pipfile for this project...\n Installing -e git+https://github.com/requests/requests.git@v2.19.1#egg=requests...\n [...snipped...]\n Adding -e git+https://github.com/requests/requests.git@v2.19.1#egg=requests to Pipfile's [packages]...\n [...]\n\nYou can read more about [pip's implementation of vcs support here](https://pip.pypa.io/en/stable/topics/vcs-support/).\n\n### Install a dev dependency:\n\n $ pipenv install pytest --dev\n Installing pytest...\n ...\n Adding pytest to Pipfile's [dev-packages]...\n\n### Show a dependency graph:\n\n $ pipenv graph\n requests==2.18.4\n - certifi [required: >=2017.4.17, installed: 2017.7.27.1]\n - chardet [required: >=3.0.2,<3.1.0, installed: 3.0.4]\n - idna [required: >=2.5,<2.7, installed: 2.6]\n - urllib3 [required: <1.23,>=1.21.1, installed: 1.22]\n\n### Generate a lockfile:\n\n $ pipenv lock\n Assuring all dependencies from Pipfile are installed...\n Locking [dev-packages] dependencies...\n Locking [packages] dependencies...\n Note: your project now has only default [packages] installed.\n To install [dev-packages], run: $ pipenv install --dev\n\n### Install all dev dependencies:\n\n $ pipenv install --dev\n Pipfile found at /Users/kennethreitz/repos/kr/pip2/test/Pipfile. Considering this to be the project home.\n Pipfile.lock out of date, updating...\n Assuring all dependencies from Pipfile are installed...\n Locking [dev-packages] dependencies...\n Locking [packages] dependencies...\n\n### Uninstall everything:\n\n $ pipenv uninstall --all\n No package provided, un-installing all dependencies.\n Found 25 installed package(s), purging...\n ...\n Environment now purged and fresh!\n\n### Use the shell:\n\n $ pipenv shell\n Loading .env environment variables...\n Launching subshell in virtual environment. Type 'exit' or 'Ctrl+D' to return.\n $ \u25af\n\n\n### PURPOSE AND ADVANTAGES OF PIPENV\n\nTo understand the problems that Pipenv solves, it's useful to show how Python package management has evolved.\n\nTake yourself back to the first Python iteration. We had Python, but there was no clean way to install packages.\n\nThen came Easy Install, a package that installs other Python packages with relative ease. But it came with a catch: it wasn't easy to uninstall packages that were no longer needed.\n\nEnter pip, which most Python users are familiar with. pip lets us install and uninstall packages. We could specify versions, run pip freeze > requirements.txt to output a list of installed packages to a text file, and use that same text file to install everything an app needed with pip install -r requirements.txt.\n\nBut pip didn't include a way to isolate packages from each other. We might work on apps that use different versions of the same libraries, so we needed a way to enable that.\n\n\nPipenv aims to solve several problems.\nFirst, the problem of needing the pip library for package installation, plus a library for creating a virtual environment, plus a library for managing virtual environments, plus all the commands associated with those libraries. That's a lot to manage. Pipenv ships with package management and virtual environment support, so you can use one tool to install, uninstall, track, and document your dependencies and to create, use, and organize your virtual environments. When you start a project with it, Pipenv will automatically create a virtual environment for that project if you aren't already using one.\n\nPipenv accomplishes this dependency management by abandoning the requirements.txt norm and trading it for a new document called a Pipfile. When you install a library with Pipenv, a Pipfile for your project is automatically updated with the details of that installation, including version information and possibly the Git repository location, file path, and other information.\n\nSecond, Pipenv wants to make it easier to manage complex interdependencies.\n\nUsing Pipenv, which gives you Pipfile, lets you avoid these problems by managing dependencies for different environments for you. This command will install the main project dependencies:\n\n pipenv install\n\nAdding the --dev tag will install the dev/testing requirements:\n\n pipenv install --dev\nTo generate a Pipfile.lock file, run:\n\npipenv lock\n\nYou can also run Python scripts with Pipenv. To run a top-level Python script called hello.py, run:\n\npipenv run python hello.py\n\nAnd you will see your expected result in the console.\n\nTo start a shell, run:\n\npipenv shell\n\nIf you would like to convert a project that currently uses a requirements.txt file to use Pipenv, install Pipenv and run:\n\npipenv install requirements.txt\n\nThis will create a Pipfile and install the specified requirements.\n\n\nDocumentation\n---------------\n\nDocumentation resides over at [pipenv.pypa.io](https://pipenv.pypa.io/en/latest/).\n\n## Star History\n\n<a href=\"https://star-history.com/#pypa/pipenv&Date\">\n <picture>\n <source media=\"(prefers-color-scheme: dark)\" srcset=\"https://api.star-history.com/svg?repos=pypa/pipenv&type=Date&theme=dark\" />\n <source media=\"(prefers-color-scheme: light)\" srcset=\"https://api.star-history.com/svg?repos=pypa/pipenv&type=Date\" />\n <img alt=\"Star History Chart\" src=\"https://api.star-history.com/svg?repos=pypa/pipenv&type=Date\" />\n </picture>\n</a>\n",
"bugtrack_url": null,
"license": "The MIT License (MIT) Copyright 2020-2022 Python Packaging Authority Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "Python Development Workflow for Humans.",
"version": "2023.12.1",
"project_urls": {
"Documentation": "https://pipenv.pypa.io/en/latest/",
"Homepage": "https://github.com/pypa/pipenv",
"Source": "https://github.com/pypa/pipenv.git"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f458a8a005cc4d4018d6a679b033c96d760fe262f361117f70f018b77e2333c6",
"md5": "15e01f8bbc26e830ff62bd2a71e822a9",
"sha256": "96c8af7c36691fbc648959f3f631954212398246c8cfcfa529ec09bc5d0bfd01"
},
"downloads": -1,
"filename": "pipenv-2023.12.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "15e01f8bbc26e830ff62bd2a71e822a9",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 3092779,
"upload_time": "2024-02-05T01:04:03",
"upload_time_iso_8601": "2024-02-05T01:04:03.918949Z",
"url": "https://files.pythonhosted.org/packages/f4/58/a8a005cc4d4018d6a679b033c96d760fe262f361117f70f018b77e2333c6/pipenv-2023.12.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "a6265cdf9f0c6eb835074c3e43dde2880bfa739daa23fa534a5dd65848af5913",
"md5": "961a6d557920c4c57cea0be0cacbb9c6",
"sha256": "4aea73e23944e464ad2b849328e780ad121c5336e1c24a7ac15aa493c41c2341"
},
"downloads": -1,
"filename": "pipenv-2023.12.1.tar.gz",
"has_sig": false,
"md5_digest": "961a6d557920c4c57cea0be0cacbb9c6",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 4538942,
"upload_time": "2024-02-05T01:04:09",
"upload_time_iso_8601": "2024-02-05T01:04:09.475335Z",
"url": "https://files.pythonhosted.org/packages/a6/26/5cdf9f0c6eb835074c3e43dde2880bfa739daa23fa534a5dd65848af5913/pipenv-2023.12.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-02-05 01:04:09",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "pypa",
"github_project": "pipenv",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "pipenv"
}
