Better virtualenv activate.

.bashrc

# Show virtual environment (if any) and git branch (if any; requires .git-prompt.sh).
source ~/.git-prompt.sh

__blank="\[\e]0;\w\a\]\n"  # white
__virtualenv=`basename "$VIRTUAL_ENV"`
__userhost="\[\e[32m\]\u@\h" # green
__pwd="\[\e[33m\]\w" # yellow
__cursor="\[\e[0m\]\n\$ " # white

export PS1="${__blank}${__virtualenv:+$__virtualenv }${__userhost} ${__pwd}\$(__git_ps1)${__cursor}"

README.markdown

Install

1. Copy inve and inve.bat (for Windows) into a destination on your $PATH.
2. Append .bashrc to your ~/.bashrc.

Usage

virtualenv [env]
inve [env]

env - name of the virtualenv environment (default: .env)

Motivation

I was persuaded by Michael Lamb's gist Virtualenv's bin/activate is Doing It Wrong and I decided to implement most of his suggestsions with a few simplifications and extensions.

Notably, I assumed a default virtual environment called .env so that I can just write inve (similar to workon from virtualenvwrapper).

inve

#!/bin/sh
__venv=".env"
if [ "$1" ]; then
  __venv="$1"
  shift
fi

if [ -d "$PWD/${__venv}" ]; then
  echo "loading virtualenv ${__venv}"
  export VIRTUAL_ENV="$PWD/${__venv}"
  export PATH="$VIRTUAL_ENV/bin:$PATH"
  unset PYTHONHOME
  exec "${@:-$SHELL}"
else
  echo "no virtualenv named ${__venv}"
  echo "try: virtualenv ${__venv}"
fi

inve.bat

@echo off
setlocal
if "%1"=="" (set "VENV=.env") else (set "VENV=%1")
if EXIST "%CD%\%VENV%" (goto load) else (goto err)

:load
  echo loading virtualenv %VENV%
  cmd /V:ON /K "set "VIRTUAL_ENV=%CD%\%VENV%\" & set "PATH=%CD%\%VENV%\Scripts;%PATH%" & set "PROMPT=%VENV% %PROMPT%" & set "PYTHONHOME=""
  goto end

:err
  echo no virtualenv named %VENV%
  echo try: virtualenv %VENV%
  echo.
:end

Revision 4

• Add: error handling for trying to load a virtual environment that doesn't exist.
• Add: console messages

Revision 5

• Fix: update branch name when switching branches