Am 21.09.2009 15:44, schrieb Allen Bierbaum:
Understood. This is a bit of a pain for people like us that are installing trac in a non-standard location and don't want to have trac plugins / extensions show up in their system wide python packages.
Of course but easy_install can install packages to any directory which is in the PYTHONPATH so you don't have to install in the system-wide package dir (I never do this personally).
However we don't advertise this because many new users are confused by that. If you know how to handle the stuff, installation to a separate directory (don't forget to set the PYTHONPATH in your fcgi wrapper script/mod_python) or installation as zipped egg is perfectly ok.
In the future if there were a way to install into the plugins directory, that would be greatly appreciated.
Actually it should work today (otherwise it's a bug) but as I said, trac does not warn you about unsatisfied dependencies + we don't test this currently.
Ok. What is the "installation" method that is used for development?
python setup.py develop --install-dir="/some/dir"
For example if we wanted to modify the code and/or add a plugin, then how would we install it into trac? With the .eggs in the plugins directory, we can put an egg link back to in development code to make changes and test them on the fly.
This is what we do as well. fs
smime.p7s
Description: S/MIME Cryptographic Signature
