kennethreitz/pipenv
1
0
Fork 0
mirror of https://github.com/kennethreitz/pipenv.git synced 2026-06-05 22:50:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

simplify

Browse Source 
Signed-off-by: Kenneth Reitz <me@kennethreitz.org>
This commit is contained in:
Kenneth Reitz
2017-09-20 13:39:36 -04:00
parent 8e5813bee6
commit ca3a0ef062
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/index.rst
+1 -1
View File
@@ -39,7 +39,7 @@ It automatically creates and manages a virtualenv for your projects, as well as
The problems that Pipenv seeks to solve are multi-faceted:
- When using Pipenv, you no longer need to use ``pip`` and ``virtualenv`` separately. They work together.
- You no longer need to use ``pip`` and ``virtualenv`` separately. They work together.
- Managing a ``requirements.txt`` file `can be problematic <https://www.kennethreitz.org/essays/a-better-pip-workflow>`_, so Pipenv uses the upcoming ``Pipfile`` and ``Pipfile.lock`` instead, which is superior for basic use cases.
- Hashes are used everywhere, always. Security.
- Give you insight into your dependency graph (e.g. ``$ pipenv graph``).