You are using this sudopybrew command WITH pythonbrew.

After you run the first "curl" command it's going to install (see that |
"pipe" to bash?)...

You can turn it off if it doesn't fix it (see the full post):

On Fri, Mar 16, 2012 at 10:52 AM, Michael Havens <bmike1@gmail.com> wrote:

> I was going to do that.... I was moving this discussion into it's own
> thread. But I did have a question about it before I installed it. It said
> that said 'After installation, where you would normally use sudo,
> non-root users will need to use sudopybrew:' is that in all instances or
> just when working with python?
>
>
> On Fri, Mar 16, 2012 at 10:47 AM, Lisa Kachold <lisakachold@obnosis.com>wrote:
>
>> This can probably be fixed via an installation of pythonbrew to create a
>> new virtualvenv:
>>
>> curl -kL http://xrl.us/pythonbrewinstall | bash
>>
>> After that, pythonbrew installs itself to ~/.pythonbrew.
>>
>> Please add the following line to the end of your ~/.bashrc:
>>
>> [[ -s $HOME/.pythonbrew/etc/bashrc ]] && source $HOME/.pythonbrew/etc/bashrc
>>
>> f the install script is run as root, pythonbrew will automatically install into /usr/local/pythonbrew.
>>
>> The pythonbrew will be automatically configured for every user on the
>> system if you install as root.
>>
>> After installation, where you would normally use sudo, non-root users
>> (which users get this error?) will need to use sudopybrew:
>> sudopybrew venv list
>> (and enter the other commands in the next section using "sudopybrew"
>> instead of "pythonbrew")
>>
>> OR if the error is incurred AS root, create isolated python environments
>> (uses virtualenv):
>>
>> pythonbrew venv init
>> pythonbrew venv create proj
>> pythonbrew venv list
>> pythonbrew venv use proj
>> pythonbrew venv delete proj
>>
>> Show version:
>>
>> pythonbrew version
>>
>> *If this does not fix your errors, it's going to be a complex packaging issue: read the links I sent and/or get someone to evaluate your packages.
>>
>> If you don't fix it with a new venv init and create/use proj (as the user you are having issues with), remember to turn it off:*
>>
>>
>> pythonbrew off
>>
>>  COMMANDS install <version>Build and install the given version of
>> python. Install setuptools and pip automatically.switch <version>Permanently
>> use the specified python as default.use <version>Use the specified
>> python in current shell.py <python file> Runs a named python file
>> against specified and/or all pythons.listList the installed all pythons.list
>> -k <version>List the available install pythons.uninstall <version> Uninstall
>> the given version of python.cleanupRemove stale source folders and
>> archives.updateUpgrades pythonbrew to the latest version.offDisable
>> pythonbrew. symlinkCreate/Remove a symbolic link to python (in a
>> directory on your $PATH)buildoutRuns the buildout with specified or
>> current using python.venvCreate isolated python environments (uses
>> virtualenv) versionShow version.See more details belowpythonbrew help
>> <command>
>> Reference:    http://pypi.python.org/pypi/pythonbrew/
>>
>> Respond with your errors at each step, if this fails?
>>
>> On Fri, Mar 16, 2012 at 10:20 AM, Michael Havens <bmike1@gmail.com>wrote:
>>
>>> python seems to be messing up. Here is the error I am getting:
>>>
>>> Traceback (most recent call last):
>>>   File "<string>", line 1, in <module>
>>> 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 "<string>", line 1, in <module>
>>> 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~(-:
>>>
>>> <From Lisa>
>>> Hi Michael,
>>>
>>> On Thu, Mar 15, 2012 at 2:07 AM, Michael Havens <bmike1@gmail.com>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 "<string>", line 1, in <module>
>>>> 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 "<string>", line 1, in <module>
>>>> 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/
>>> <http://farmdev.com/thoughts/76/the-python-packaging-problem/%20>
>>>
>>> There is more available here, suggesting that you use pythonbrew<https://github.com/utahta/pythonbrew>and 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~(-:
>>>
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>>
>>
>>
>>
>> --
>> (503) 754-4452 Android
>> (623) 239-3392 Skype
>> (623) 688-3392 Google Voice
>> **
>> it-clowns.com
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>
>
>
>
> --
> :-)~MIKE~(-:
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>



-- 
(503) 754-4452 Android
(623) 239-3392 Skype
(623) 688-3392 Google Voice
**
it-clowns.com