fix for issue #5

Author: dhellmann

README

@@ -130,6 +130,10 @@ For more details, refer to the column published in the May 2008 issue of Python
 Updates
 =======
 
+1.13
+  - Fix issue #5 by correctly handling symlinks and limiting the list of envs to things 
+    that look like they can be activated.
+
 1.12
   - Check return value of virtualenvwrapper_verify_workon_home everywhere, thanks to 
     Jeff Forcier for pointing out the errors.

pavement.py

@@ -22,7 +22,7 @@
 
 # What project are we building?
 PROJECT = 'virtualenvwrapper'
-VERSION = '1.12'
+VERSION = '1.13'
 
 # Read the long description to give to setup
 README_FILE = 'README'

test.sh

@@ -63,13 +63,17 @@ virtualenvwrapper_verify_active_environment && echo "FAIL" || echo "PASS"
 
 echo
 echo "LISTING ENVIRONMENTS"
+mkdir -p "$WORKON_HOME/extra/bin"
+touch "$WORKON_HOME/extra/bin/activate"
+(cd "$WORKON_HOME"; ln -s extra link)
 envs=`workon | tr '\n' ' '`
 echo "Found environments: $envs"
-if [ "$envs" = "env1 env2 " ]
+if [ "$envs" = "env1 env2 extra link " ]
 then
     echo "PASS"
 else
     echo "FAIL: \""$envs\"""
+    ls -l "$WORKON_HOME"
 fi
 
 echo

virtualenvwrapper_bashrc

@@ -115,7 +115,7 @@ function rmvirtualenv () {
 # List the available environments.
 function virtualenvwrapper_show_workon_options () {
     virtualenvwrapper_verify_workon_home || return 1
-	find "$WORKON_HOME" -maxdepth 1 -mindepth 1 -type d -exec basename '{}' \; | sort
+    (cd "$WORKON_HOME"; ls */bin/activate) | sed 's|/bin/activate||' | sort
 }
 
 # List or change working virtual environments