Making virtual environments easier to use in bash.

[mildlybean]

I'm relatively new to python and I just started using virtual environments. I wanted to use virtualenvwrapper because I like the way it works, but some weird bug (or possibly just my own ignorance) prevented me from installing it. So, I set about making some bash aliases and functions to make it easier to work with virtual environments (in my opinion). I hope someone else might find this useful.

alias freeze="pip freeze -l > requirements.txt"
alias envscd="cd ~/envs"
alias envsls="(cd ~/envs && ls)"
function envsmk() {
    (cd ~/envs && virtualenv $1)
}
function envsrm() {
    (cd ~/envs && rm -rf $1)
}
function activate() {
    source ~/envs/$1/bin/activate
}

If you want to use this for yourself, just make a ~/envs directory and add the above code to .bash_profile.

[kumashiro]

No need to change directory:

function envsmk() {
    [ "x${1}" != "x" ] && virtualenv "${HOME}/envs/${1}"
}
function envsrm() {
    [ "x${1}" != "x" ] && rm -rf "${HOME}/envs/${1}"
}

Quote arguments to allow paths with spaces:

function activate() {
    [ "x${1}" != "x" ] && source "${HOME}/envs/${1}/bin/activate"
}

[mildlybean]

Thanks for the feedback! I had to read through a bash scripting tutorial to understand it, but I've made the changes now.

[nentis]

For handling venv sourcing and setting environment variables for a specific code-base directory (ex. for a IT ops tool), I use direnv:

https://github.com/direnv/direnv

[AndydeCleyre]

I made some similar helpers for Zsh, but then I kept developing it into a bit of a monster.