chpwd hook for automatically activating and deactivating virtualenvs, and added option to load virtualenvwrapper normally(as opposed to lazy).
more info in README.md :)
Automatic virtualenv activaiion and deactivation, virtualenv non lazy
Can automatically activating and deactivating virtualenvs interfere with currently running process or projects causing issues. Under what circumstances can this cause issues?
The only way I can imagine it interfering is if the user manually activates a virtualenv, in those cases this extension does not function.
Does this affect presently running applications/servers?
I've been looking at random Python projects. Sometimes, .venv is a file; other times, it's a directory.
Activating virtualenvs only affect the current shell session, so I don't think it will interfere with running applications, servers.
We could add an option to customize the name of the file, to use something other than .venv
I would rather have a standard like .RUBY_VERSION.
I don't beleive there is any convention for python virtualenvs. However, oh my zsh uses .venv as the file name for this purpose.
The example in the 'tips and tricks' section of virtualenvwrapper's docs uses a .venv file for this functionality.
I'm deleting this pull request to pursue a more general alternative such as zsh-autoenv.