Rethink setup.py with Pipfile
As setup.py can be explicitly installed or not from a Pipfile I reasoned
that it should not be installed by default after pipenv has used
relevant Pipfiles.
RENAME
tests/venv/pipfile/setup-py/Pipfile
tests/venv/pipfile/setup-py-explicit/Pipfile
@@ -4,7 +4,5 @@ verify_ssl = true
name = "pypi"
[packages]
-requests = "*"
-
-[dev-packages]
there = "*"
+dummy = {path=".", editable=true}

ADD
tests/venv/pipfile/setup-py-explicit/README.rst
+Python - Pipfile + setup.py
+---------------------------
+
+The Pipfile asked the local package to be installed with ``setup.py``, was it?

RENAME
tests/venv/pipfile/setup-py/dummy/__init__.py
tests/venv/pipfile/setup-py-explicit/dummy/__init__.py
RENAME
tests/venv/pipfile/setup-py/setup.py
tests/venv/pipfile/setup-py-explicit/setup.py
RENAME
tests/venv/pipfile/setup-py/verify
tests/venv/pipfile/setup-py-explicit/verify
#!/usr/bin/env python
-import requests
import there
import dummy

DELETE
tests/venv/pipfile/setup-py/README.rst
-Python - Pipfile(.lock) + setup.py
-----------------------------------
-
-We should make ``setup.py`` be installed after the ``Pipfile`` or
-``Pipfile.lock``.

Rethink setup.py with Pipfile

As setup.py can be explicitly installed or not from a Pipfile I reasoned
that it should not be installed by default after pipenv has used
relevant Pipfiles.