Eirik Schwenke-2 wrote:
> 
> That error doesn't make much sense to me ... unless you've hit sudo by
> accident, and /home/rjollos/.python-eggs is owned by root ?
> 

The first thing I realized is that I need to run `source bin/activate` each
time I open a shell in order to start working in the virtual environment.

Second, I got pretty stuck on the idea that the .python-eggs directory
should be written into the virtual environment rather than my home
directory, but that does not seem to be the case.  You were right, it turned
out to be a permissions issue.

Even though the `.egg` files were owned by the user I was logged in as, the
~/.python-eggs directory was owned by root, no doubt caused by prefixing the
sudo command to every command when setting up the development environment,
which caused me all sorts of issues.  The reason I started doing that was
the first command `python -m easy_install virtualenv` failed when not run as
root, and I didn't really think through what was going on here.

My understanding of it now is that virtualenv needs to be installed
globally, but all of the commands after that involve installing in the home
directory of a user.


Eirik Schwenke-2 wrote:
> 
> I just ran through the steps outlined in [1] now; and found I had to
> init the virtualenv without global site packages, and locally upgrade
> setuptools in the virtualenv:
> 

I also installed virtualenv with the 'no global packages' option.  The
virtualenv seems to work fine for me without upgrading any packages within
the virutalenv.  It installs setup_tools 0.6c11.  Maybe this depends on
which version of `virtualenv` that you install?


Eirik Schwenke-2 wrote:
> 
> Perhaps --no-site-packages should be added to the wiki ? I have a bit of
> a hodgepodge system more-or-less running debian/testing (squeeze) -- so
> my problems with packages might not be entirely representative...
> 

The use of the `--no-site-packages` option is documented in the 'Setup a
Virtual Environment' section.  It is documented after the list of commands,
so it is easy to miss.

http://trac.edgewall.org/wiki/TracDev/DevelopmentEnvironmentSetup#Setupavirtualenvironment

Thank you for the valuable help!  I think I am up and running now, though I
would like to get the Eclipse IDE working with this as well so I still have
that step to accomplish.
-- 
View this message in context: 
http://old.nabble.com/Questions-about-setting-up-Trac-development-environment-tp27011625p27026801.html
Sent from the Trac Dev mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en.


Reply via email to