Fixed bug with virtualenvwrapper and set -e

Virtualenvwrapper does some fairly funky stuff, and one of the things it does
renders it incompatible with a script run with set -e the first time it creates a virutal environment.

I'm unsetting -e each time I interact with virtualenvwrapper