You should confirm that the python executable in the venv is actually Python 2.7, which you can do by running
~/env_dir/python -V ~/env_dir/python2.7 -V (both of those files should exist, and you can run the above without activating the virtualenv, as you're specifying the exact path). If either of them shows Python 3 as the version, then your installation is not working correctly. It may be that Debian has somehow patched things in a way that's causing the issue - you say "the default Python is Python 3.4.2" - does Debian make that happen by some symlink juggling that might be causing issues here? (I know almost nothing about how Linux distros patch upstream tools, but we have had issues in the past which have ended up being related to patches applied on Debian). Paul -- You received this message because you are subscribed to the Google Groups "virtualenv" group. To unsubscribe from this group and stop receiving emails from it, send an email to python-virtualenv+unsubscr...@googlegroups.com. To post to this group, send email to python-virtualenv@googlegroups.com. Visit this group at https://groups.google.com/group/python-virtualenv. For more options, visit https://groups.google.com/d/optout.
