Un-vendor Pew

docs/advanced.rst

@@ -382,7 +382,7 @@ will detect it.
     - ``PIPENV_SHELL_FANCY`` — Always use fancy mode when invoking ``pipenv shell``.
 
     - ``PIPENV_VENV_IN_PROJECT`` — If set, use ``.venv`` in your project directory
-      instead of the global virtualenv manager ``pew``.
+      instead of a global location.
 
     - ``PIPENV_COLORBLIND`` — Disable terminal colors, for some reason.
 
@@ -424,8 +424,9 @@ For example::
 ☤ Custom Virtual Environment Location
 -------------------------------------
 
-Pipenv's underlying ``pew`` dependency will automatically honor the ``WORKON_HOME`` environment
-variable, if you have it set — so you can tell pipenv to store your virtual environments wherever you want, e.g.::
+Pipenv automatically honors the ``WORKON_HOME`` environment variable, if you
+have it set — so you can tell pipenv to store your virtual environments
+wherever you want, e.g.::
 
     export WORKON_HOME=~/.venvs
 

docs/requirements.txt

@@ -10,7 +10,6 @@ imagesize==0.7.1
 Jinja2==2.9.6
 MarkupSafe==1.0
 pbr==3.1.1
-pew==0.1.26
 pip-tools==1.9.0
 -e .
 Pygments==2.2.0