You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/dev/philosophy.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ Pipenv is an open but opinionated tool, created by an open but opinionated devel
7
7
Management Style
8
8
~~~~~~~~~~~~~~~~
9
9
10
-
`Kenneth Reitz <http://kennethreitz.org>`_ is the BDFL. He has final say in any decision related to the Pipenv project. Kenneth is responsible for the direction and form of the library, as well as its presentation. In addition to making decisions based on technical merit, he is responsible for making decisions based on the development philosophy of Pipenv.
10
+
`Kenneth Reitz <http://kennethreitz.org>`__ is the BDFL. He has final say in any decision related to the Pipenv project. Kenneth is responsible for the direction and form of the library, as well as its presentation. In addition to making decisions based on technical merit, he is responsible for making decisions based on the development philosophy of Pipenv.
11
11
12
-
`Dan Ryan<http://github.com/techalchemy>`_, `Tzu-ping Chung<https://github.com/uranusjr>`_, and `Nate Prewitt<https://github.com/nateprewitt>`_ are the core contributors.
12
+
`Dan Ryan<http://github.com/techalchemy>`__, `Tzu-ping Chung<https://github.com/uranusjr>`__, and `Nate Prewitt<https://github.com/nateprewitt>`__ are the core contributors.
13
13
They are responsible for triaging bug reports, reviewing pull requests and ensuring that Kenneth is kept up to speed with developments around the library.
14
14
The day-to-day managing of the project is done by the core contributors. They are responsible for making judgements about whether or not a feature request is
:ref:`Pipenv` is a dependency manager for Python projects. If you're familiar
73
+
Pipenv is a dependency manager for Python projects. If you're familiar
75
74
with Node.js' `npm`_ or Ruby's `bundler`_, it is similar in spirit to those
76
-
tools. While :ref:`pip` can install Python packages, Pipenv is recommended as
75
+
tools. While pip can install Python packages, Pipenv is recommended as
77
76
it's a higher-level tool that simplifies dependency management for common use
78
77
cases.
79
78
80
-
Use ``pip`` to install Pipenv:
79
+
.. _npm: https://www.npmjs.com/
80
+
.. _bundler: http://bundler.io/
81
+
81
82
82
-
.. code-block:: python
83
+
☤ Homebrew Installation of Pipenv
84
+
---------------------------------
85
+
86
+
Homebrew is a popular open-source package management system for macOS.
87
+
88
+
Installing pipenv via Homebrew will keep pipenv and all of its dependencies in
89
+
an isolated virtual environment so it doesn't interfere with the rest of your
90
+
Python installation.
91
+
92
+
Once you have installed `Homebrew`_ simply run::
93
+
94
+
$ brew install pipenv
95
+
96
+
To upgrade pipenv at any time::
97
+
98
+
$ brew upgrade pipenv
83
99
84
-
$ pip install --user pipenv
85
100
101
+
☤ Pragmatic Installation of Pipenv
102
+
----------------------------------
103
+
104
+
If you have a working installation of pip, and maintain certain "toolchain" type Python modules as global utilities in your user environment, pip `user installs <https://pip.pypa.io/en/stable/user_guide/#user-installs>`_ allow for installation into your home directory. Note that due to interaction between dependencies, you should limit tools installed in this way to basic building blocks for a Python workflow like virtualenv, pipenv, tox, and similar software.
86
105
106
+
To install::
107
+
108
+
$ pip install --user pipenv
87
109
88
110
.. Note:: This does a `user installation`_ to prevent breaking any system-wide
89
111
packages. If ``pipenv`` isn't available in your shell after installation,
@@ -105,32 +127,43 @@ Use ``pip`` to install Pipenv:
105
127
user ``PATH`` permanently in the `Control Panel`_. You may need to log
106
128
out for the ``PATH`` changes to take effect.
107
129
108
-
.. _npm: https://www.npmjs.com/
109
-
.. _bundler: http://bundler.io/
130
+
For more information, see the `user installs documentation <https://pip.pypa.io/en/stable/user_guide/#user-installs>`_.
Pipenv manages dependencies on a per-project basis. To install packages,
119
156
change into your project's directory (or just an empty directory for this
120
-
tutorial) and run:
121
-
122
-
.. code-block:: bash
157
+
tutorial) and run::
123
158
124
159
$ cd myproject
125
160
$ pipenv install requests
126
161
127
162
Pipenv will install the excellent `Requests`_ library and create a ``Pipfile``
128
-
for you in your project's directory. The :ref:`Pipfile` is used to track which
163
+
for you in your project's directory. The ``Pipfile`` is used to track which
129
164
dependencies your project needs in case you need to re-install them, such as
130
165
when you share your project with others. You should get output similar to this
131
-
(although the exact paths shown will vary):
132
-
133
-
.. code-block:: text
166
+
(although the exact paths shown will vary)::
134
167
135
168
Creating a Pipfile for this project...
136
169
Creating a virtualenv for this project...
@@ -161,7 +194,7 @@ when you share your project with others. You should get output similar to this
161
194
162
195
163
196
☤ Using installed packages
164
-
--------------------------
197
+
==========================
165
198
166
199
Now that Requests is installed you can create a simple ``main.py`` file to
167
200
use it:
@@ -174,9 +207,7 @@ use it:
174
207
175
208
print('Your IP is {0}'.format(response.json()['origin']))
176
209
177
-
Then you can run this script using ``pipenv run``:
178
-
179
-
.. code-block:: bash
210
+
Then you can run this script using ``pipenv run``::
180
211
181
212
$ pipenv run python main.py
182
213
@@ -192,57 +223,6 @@ have access to your installed packages with ``$ pipenv shell``.
192
223
193
224
194
225
☤ Next steps
195
-
------------
226
+
============
196
227
197
228
Congratulations, you now know how to install and use Python packages! ✨ 🍰 ✨
198
-
199
-
.. _proper_installation:
200
-
201
-
202
-
☤ Homebrew Installation of Pipenv
203
-
=================================
204
-
205
-
Homebrew is a popular open-source package management system for macOS.
206
-
207
-
Installing pipenv via Homebrew will keep pipenv and all of its dependencies in
208
-
an isolated virtual environment so it doesn't interfere with the rest of your
209
-
Python installation.
210
-
211
-
Once you have installed `Homebrew <https://brew.sh/>`_ simply run::
212
-
213
-
$ brew install pipenv
214
-
215
-
To upgrade pipenv at any time::
216
-
217
-
$ brew upgrade pipenv
218
-
219
-
.. _pragmatic_installation:
220
-
221
-
☤ Pragmatic Installation of Pipenv
222
-
==================================
223
-
224
-
If you have a working installation of pip, and maintain certain "toolchain" type Python modules as global utilities in your user environment, pip `user installs <https://pip.pypa.io/en/stable/user_guide/#user-installs>`_ allow for installation into your home directory. Note that due to interaction between dependencies, you should limit tools installed in this way to basic building blocks for a Python workflow like virtualenv, pipenv, tox, and similar software.
225
-
226
-
To install::
227
-
228
-
$ pip install --user pipenv
229
-
230
-
For more information see the `user installs documentation <https://pip.pypa.io/en/stable/user_guide/#user-installs>`_, but to add the installed cli tools from a pip user install to your path, add the output of::
0 commit comments