@@ -101,19 +101,20 @@ If the Homebrew version of Python 2 is installed then ``pip2`` will point to Pyt
101
101
If the Homebrew version of Python 3 is installed then ``pip3 `` will point to Python 3.
102
102
103
103
104
- Virtual Environments
105
- --------------------
104
+ Pipenv & Virtual Environments
105
+ -----------------------------
106
106
107
- A Virtual Environment (commonly referred to as a 'virtualenv') is a tool to keep
108
- the dependencies required by different projects in separate places, by creating
109
- virtual Python environments for them. It solves the "Project X depends on
110
- version 1.x but, Project Y needs 4.x" dilemma, and keeps your global
111
- site-packages directory clean and manageable.
107
+ The next step it to install Pipenv, so you can install dependencies and manage virtual environments.
108
+
109
+ A Virtual Environment is a tool to keep the dependencies required by different projects
110
+ in separate places, by creating virtual Python environments for them. It solves the
111
+ "Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps
112
+ your global site-packages directory clean and manageable.
112
113
113
114
For example, you can work on a project which requires Django 1.10 while also
114
115
maintaining a project which requires Django 1.8.
115
116
116
- To start using this and see more information: : ref: `Virtual Environments <virtualenvironments-ref >` docs.
117
+ So, onward! To the : ref: `Pipenv & Virtual Environments <virtualenvironments-ref >` docs!
117
118
118
119
--------------------------------
119
120
0 commit comments