Detect the .venv in any parent directory of the current directory

[cbazin]

This patch allow the autoactivation of virtualenv in any parent directory.

This is useful when the .venv directory is not at the root of the git repository.

In addition, it works even if the .venv is not in a git repository.

[jdutriaux]

👍

[Blist]

useful feature when you work with many .venv in a project

[ParthKolekar]

Breaks a feature....
For some reason, mkvirtualenv makes the environments in $HOME/.virtualenvs/$PROJECT_NAME/
There is not .venv there.

OS: Ubuntu 14.04 LTS
virtualenv: 12.1.1
zsh: zsh 5.0.2 (x86_64-pc-linux-gnu)
oh-my-zsh: master

[jdutriaux]

See PR #4025.

[ncanceill]

@cbazin please address this coment.

[jacobsvante]

It's at times like these I wish that the project had a test suite.

[lilorox]

This completely breaks the plugin on Ubuntu. Besides the realpath executable issue, since I don't use .venv files in my projects, the script never detects my virtualenv.

[osleg]

This patch breaking auto activation of venv without .venv by directory name

[apjanke]

@osleg, @lilorox: PR #4122 makes git repos without .venv subdirs work again, and should fix your problems. Could you test that out and see if it works for you?

[apjanke]

@ParthKolekar: mkvirtualenv is part of the main virtualenv distribution, not this oh-my-zsh plugin. Are you sure it was working before? Check the value of your $WORKON_HOME environment variable, which determines where your virtualenvs will be created by default.