Support a target directory for vendoring (similar to pip --target)

We currently vendor some of our dependencies to a target directory, using pip install -t. It would be great for pipenv to support this functionality! This is our main blocker to further use.

I think right now it may be possible to accomplish by having pipenv generate a requirements.txt and pass it to pip to do the install, but that’s very manual, and loses features like integrity-checking, so it would be much nicer for pipenv to do it.

(I mentioned this at PyCon, just wanted to make a github issue too so I can follow it.)

[scoates]

Now that there’s new Pipenv momentum, and some of the leadership appears to have changed, is there any way we could reopen this issue? As far as we can tell from the comments here, this was never resolved, and was somehow opaquely moved to a secret tracker.

At the very least, could we track this in public, please?

[uranusjr]

You can use this as a work around:

$ pipenv lock -r > /somewhere-temporary/requirements.txt   # Use -d if you want dev-packages as well.
$ pipenv run pip install -t -r /somewhere-temporary/requirements.txt