`pip install` from Pypi does not install dependencies

Hello

I really prefer pipenv to handle Pipfile and Pipfile.lock over the old requirements.txt, however, my packages that uses pipenv (ex: here), when installed with pip install txrwlock, get no dependency at all.

I wonder if, for the moment at least, auto-generating a requirements.txt is not necessary, at least waiting for official support of Pipfile by pip (and other tools such as ReadTheDoc or Pyup that only support requirements.txt).

What’s your thoughts?

[vphilippon]

I do not see a need to auto-generate requirements.txt, that could actually cause some conflict with an existing requirements.txt in the directory and such.

We can generate a requirements.txt with pipenv lock --requirements > requirements.txt, so the option is there for anyone needing a requirements.txt for system on which they can’t install Pipenv, until pip supports Pipfile/Pipfile.lock.

[gsemet]

Donc in #967 😃

I don’t use pyenv, only brew python on my mac and default python 2.7 on ubuntu 16.04. I have seen this behavior on both the Travis build and my local machine. I also have some instabilities of pipenv on Python 2.7 (see the various executions in here), but if you tell me it is not officially supported that would be a totally acceptable response. I am not sure this instability on the Travis build is due to pipenv of by travis it self (bad infra?)