Env activation command

[taha-yassine]

I use virtualenvwrapper to manage my Python envs. The command to activate an env is workon, but the extension seems to directly source the activation script instead. This works for activating the env but fails to trigger hook scripts which I rely on to set some environment variables. The workaround is to manually activate the env in the current terminal using workon, but it's not very practical. The same problem happens when working with Jupyter notebooks/interactive scripts. Is there a way I can manually configure the activation command or should I report this as a bug?

[brettcannon]

There isn't a way to control the activation command (you can turn it on or off), but please open a feature request and not a bug if you want tighter integration with virtualenvwrapper.