Automatic virtualenv activation and deactivation, virtualenv non lazy mode. #517

Closed
wants to merge 1 commit into
from

Projects

None yet

2 participants

@jck
jck commented Dec 20, 2013

chpwd hook for automatically activating and deactivating virtualenvs, and added option to load virtualenvwrapper normally(as opposed to lazy).

more info in README.md :)

@sorin-ionescu
Owner

Can automatically activating and deactivating virtualenvs interfere with currently running process or projects causing issues. Under what circumstances can this cause issues?

@jck
jck commented Jan 4, 2014

The only way I can imagine it interfering is if the user manually activates a virtualenv, in those cases this extension does not function.

@sorin-ionescu
Owner

Does this affect presently running applications/servers?

@sorin-ionescu
Owner

I've been looking at random Python projects. Sometimes, .venv is a file; other times, it's a directory.

@jck
jck commented Jan 10, 2014

Activating virtualenvs only affect the current shell session, so I don't think it will interfere with running applications, servers.

@jck
jck commented Jan 10, 2014

We could add an option to customize the name of the file, to use something other than .venv

@sorin-ionescu
Owner

I would rather have a standard like .RUBY_VERSION.

@jck
jck commented Jan 10, 2014

I don't beleive there is any convention for python virtualenvs. However, oh my zsh uses .venv as the file name for this purpose.

@jck
jck commented Feb 7, 2014

The example in the 'tips and tricks' section of virtualenvwrapper's docs uses a .venv file for this functionality.

http://virtualenvwrapper.readthedocs.org/en/latest/tips.html

@jck
jck commented Feb 1, 2015

I'm deleting this pull request to pursue a more general alternative such as zsh-autoenv.

@jck jck closed this Feb 1, 2015
@jck jck deleted the jck:python-autoenv branch Feb 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment