python seems to be messing up. Here is the error I am getting: Traceback (most recent call last): File "", line 1, in ImportError: No module named virtualenvwrapper.hook_loader virtualenvwrapper.sh: There was a problem running the initialization hooks. If Python could not import the module virtualenvwrapper.hook_loader, check that virtualenv has been installed for VIRTUALENVWRAPPER_PYTHON=/usr/bin/python and that PATH is set properly. Traceback (most recent call last): File "", line 1, in ImportError: No module named virtualenvwrapper.hook_loader virtualenvwrapper.sh: There was a problem running the initialization hooks. If Python could not import the module virtualenvwrapper.hook_loader, check that virtualenv has been installed for VIRTUALENVWRAPPER_PYTHON=/usr/bin/python and that PATH is set properly. Why is it repeating the 'call'? Could you tell me how to fix it: -- :-)~MIKE~(-: Hi Michael, On Thu, Mar 15, 2012 at 2:07 AM, Michael Havens wrote: > I want to copy a folder from Michaels-Laptop to Michaels-PC across the > network. I am logged in to Michaels-Laptop via ssh on the PC. WHat am I > doing wrong? > > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named virtualenvwrapper.hook_loader > virtualenvwrapper.sh: There was a problem running the initialization > hooks. If Python could not import the module virtualenvwrapper.hook_loader, > check that virtualenv has been installed for > VIRTUALENVWRAPPER_PYTHON=/usr/bin/python and that PATH is set properly. > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named virtualenvwrapper.hook_loader > virtualenvwrapper.sh: There was a problem running the initialization > hooks. If Python could not import the module virtualenvwrapper.hook_loader, > check that virtualenv has been installed for > VIRTUALENVWRAPPER_PYTHON=/usr/bin/python and that PATH is set properly. > This "ImportError: No module named virtualenvwrapper.hook_loader" looks like a virtualenv python packaging problem: http://farmdev.com/thoughts/76/the-python-packaging-problem/ There is more available here, suggesting that you use pythonbrewand the newer command "venv" to manage your python modules: http://ubuntuforums.org/showthread.php?t=1571347 Here's a quick pythonbrew/venv module how to: http://pypi.python.org/pypi/pythonbrew/ It's a good possibility that it's not setup for system wide users (make sure you change to use the same version numbers for your install). If you get the same errors, this is the packaging problem where virtualenv has broken dependencies. -- :-)~MIKE~(-: