On 16 January 2018 at 14:24, Nick Coghlan <ncogh...@gmail.com> wrote: > On 16 January 2018 at 05:46, Brett Cannon <br...@python.org> wrote: >> On Mon, 15 Jan 2018 at 00:33 Chris Withers <ch...@withers.org> wrote: >>> Continuing on the deployment theme: I'm used to being able to put >>> /path/to/some/ve/bin/some_script in crontabs and the like, where >>> some_script comes form a setuptools entry point. >>> What's the canonical way of doing this with pipenv? >> >> Beats me. I think there's a command to get back to the venv that pipenv >> created on your behalf. > > "pipenv --venv" gives the path for the current project, so what I tend > to do is run "ls -s $(pipenv --venv) .venv" from the directory > containing Pipfile and Pipfile.lock in order to create a deterministic > path name.
Oops, that should have been "ln -s $(pipenv --venv) .venv". Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
