> Tim Hatch wrote: >> >> The problem is that you're running tracd, which is shared systemwide. >> For development, the equivalent command is trac/web/standalone.py, which >> should work with whatever version is in your path/virtualenv. >> > > That is interesting, and seems to work. > > I'm not sure what you mean by tracd being shared system-wide. I have > installed Trac in a virtualenv, there is a tracd located at > `<PathToVirtualEnv>/bin/tracd`, and `which tracd` points to that instance of > tracd once I have run `source bin/activate`. > > If that really is the preferred way of starting the Trac for development, it > seems like it should be documented here [1].
It's just a simpler way, if you're managing a large number of parallel checkouts, or need a streamlined way to set up a clean state every time (i.e. buildbots) > There is no documentation in the file `standalone.py`, and a search of the > wiki [2] doesn't reveal much useful information, so I have to ask ... what > is the different between running `standalone.py` and `tracd`? They're equivalent, the only difference being that tracd has another layer of indirection, and checks the setuptools metadata earlier. If you check setup.py, it contains the following line: tracd = trac.web.standalone:main Tim
-- 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.
