Hi. > Michael Renzmann wrote: >> ... Not using BASELINE (or creating >> it with site-packages) wouldn't work since the site-wide Python >> installation has trac and other stuff in the site-packages. > This not my experience. [...]
Thanks for the hint. And it turned out that the above indeed was wrong. The fix for the problem I've described was pretty simple in the end: 1. The Subversion bindings were not visible inside the virtualenv I've created. In contrast to what was stated in a related thread on trac-users [1], things didn't even work when creating a virtualenv WITH site-packages (by omitting the --no-site-packages parameter). But what worked was to create the file <virtualenv>/lib/python2.5/site-packages/python-subversion.pth with the following content: === cut === /usr/share/python-support/python-subversion /usr/lib/python-support/python-subversion/python2.5/libsvn === cut === 2. The other issue (which showed up right after solving the subversion bindings thing) was a missing symlink for clearsilver. Fixed with: ln -s /usr/lib/python2.5/site-packages/neo_cgi.so <virtualenv>/lib/site-packages/python2.5/site-packages/neo_cgi.so Long story short: Trac 0.10 is now virtualenv'ed in the cloned t-h.o vserver, which tomorrow morning will replace the old t-h.o vserver. Once that is done, I'll take care of Trac 0.11 in a separate virtualenv on the same vserver. Bye, Mike [1] http://groups.google.com/group/trac-users/browse_thread/thread/4486d9042fc62d7c _______________________________________________ th-users mailing list [email protected] https://lists.trac-hacks.org/mailman/listinfo/th-users
