Add an equivalent of `workon` from virtualenvwrapper

Workon does two things. When executed with no args, it lists all available projects (i.e. venvs).

More helpfully, it streamlines the activation process when opening a new shell. This is super useful if you have dozens of projects you work on regularly. A possible syntax for pipenv could look like this:

~ $ pipenv work
blog
django
requests
supersecretproject
pipenv
~ $ pipenv work requests
Moving you to the requests project and activating the shell
(requests) ~/code/requests $

(PS1’s might not be right for pipenv behaviour, but you get the idea.

This streamlines the developers’ flow from:

cd code/requests
pipenv shell

to just:

pipenv work requests

It’s a minor enhancement but something I’d miss moving from virtualenvwrapper.

[ashwinvis]

@kennethreitz @fweidemann14 @kblicharski, I finally understood. Here is a short rosetta, for someone who is as new to pew and pipenv as me.

virtualenvwrapper + pip	pew + pipenv
mkvirtualenv	pew new
cpvirtualenv	pew cp
lsvirtualenv	pew ls
workon	pew workon
deactivate	Ctrl + D / exit
pip install	pipenv install

A few gotchas:

• The cdproject equivalent from virtualenvwrapper is missing. But pew setproject can do the change to directory once.
• pew new does not have a --system-site-packages option. Instead there is a separate pew toggleglobalsitepackages command.

[filipweidemann]

@kennethreitz Is this feature still a thing? I really love Pipenv and recently converted all my projects, but an equivalent to virtualenvwrapper’s workon would really add that last bit of luxury to it. You should consider adding it 😉