Grzegorz Sobanski wrote: > > As seen here it tries to install into /usr/local and not into your > virtual env. > Did you run 'setup.py develop' from the shell where you did > 'source bin/activate'? > > When you want to work with your virtual env you always have to issue > a 'source bin/activate' in that shell. >
I appears that I messed up installation into a virtual env. I will give that a try once again. Thanks! Noah Kantrowitz-3 wrote: > > > Make that a PythonOption. Its a long story involving setuptool's > braindead init framework. > > On a related note, you really don't want to use mod_py for > development. You want to use tracd. For an example dev environment, > look at https://coderanger.net/svn/projects/trac/devenv/ > > Now that you mention, I think that I'm not using mod_py, which explains why the option wasn't taking effect. How would I go about setting PYTHON_EGG_CACHE as a python option? (I'm just starting to learn the python language and haven't reached that chapter in the book yet ;) Thank you for your time! -- View this message in context: http://old.nabble.com/Questions-about-setting-up-Trac-development-environment-tp27011625p27019869.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.
