On Fri, Mar 16, 2012 at 6:56 PM, Michael Havens <bmike1@gmail.com> wrote:

well.... I almost made it through your instructions. I got as far as:

bmike1@Michaels-Laptop ~ $ sudopybrew venv use proj
# Using `proj` environment (found in /home/bmike1/.pythonbrew/venvs/Python-2.7.2)
# To leave an environment, simply run `deactivate`
bash: /home/bmike1/.pythonbrew/etc/venv.run: Permission denied
(proj)bmike1@Michaels-Laptop

Is it supposed to give that error?

1) How many python installs do you find?

# locate python |more

2) What is your PATH now? After you edited your .bashrc to add the environmental variable did you invoke it?

# /bin/bash

Run it again and see if that fixed it

3) A child process can't fork here, so bash can't run or write to venv.run (known error). I would try it simply with:

sudo pythonbrew venv use proj

So now try your original command (that gave the error) now and see if you are still getting a python error?

On Fri, Mar 16, 2012 at 3:52 PM, Lisa Kachold <lisakachold@obnosis.com> wrote:
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.
list
List the installed all pythons.
list -k <version>
List the available install pythons.
uninstall <version>

Uninstall the given version of python.
cleanup
Remove stale source folders and archives.
update
Upgrades pythonbrew to the latest version.
off
Disable pythonbrew.
symlink
Create/Remove a symbolic link to python (in a directory on your $PATH)
buildout
Runs the buildout with specified or current using python.
venv
Create isolated python environments (uses virtualenv)

version
Show version.
See more details below
pythonbrew 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/

There is more available here, suggesting that you use 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
---------------------------------------------------
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