Thanks, I'll take a look at that. I was trying to test both from the work and virtualenv, but I'll definitely check that out.
Thanks, Jerry On May 10, 2:54 pm, Christian Boos <[email protected]> wrote: > jerry wrote: > > I have a patch I developed, and I would like to run the trac unit > > tests to make sure I haven't broken anything. But when I try to run > > the unit tests following the instructions on the wiki at wiki/TracDev/ > > UnitTests, I can't. I get an import error that I haven't been able to > > make go away. > > > I don't know if it is a trac problem, or a python problem, or if I > > have borked my version of python or trac, or if I am just borked in > > the head. Cause I am still a trac and python newbie. > > > Here is the error. It is with Trac 0.11.1, running on Centos 5, and > > on Python 2.4.3. > > > [r...@kermit trac-0.11.1]# PYTHONPATH=. trac/test.py > > Traceback (most recent call last): > > ... > > import trac.tests > > ImportError: No module named tests > > [r...@kermit trac-0.11.1]# > > > The symptoms seem to be that PYTHONPATH is being ignored. > > Right, this is due to some magic performed by setuptools (have a look at > the first and last lines of the > /usr/lib/python2.4/lib/python2.4/site-packages/easy-install.pth file). > > This is quite annoying, as this makes it difficult to test a particular > Trac checkout once you have already installed another version in the > standard location. Either uninstall Trac and use only Trac from the > working copy, or use virtualenv. > > -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
