Am 13.01.2006 um 18:36 schrieb Carl Risberg:
(Now at home, I will soon check what happens also on my Ubuntu
Breezy box)
Yepp, Same phenomena on Ubuntu. Some dir listings...
[EMAIL PROTECTED]:/var/lib/trac$ ls */plugins
Proj1/plugins:
Proj2/plugins:
TracAccountManager-0.1.2-py2.4.egg
- - -
[EMAIL PROTECTED]:/var/lib/trac$ ls /usr/lib/python2.4/site-packages/*.egg
/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.1dev_r2765-
py2.4.egg /usr/lib/python2.4/site-packages/TracWikiGoodies-0.2-
py2.4.egg
/usr/lib/python2.4/site-packages/setuptools-0.6a9-py2.4.egg:
easy_install.py easy_install.pyc EGG-INFO pkg_resources.py
pkg_resources.pyc setuptools site.py site.pyc
...but still WebAdmin/plugins in Proj1 shows all three plugins (+
trac 0.9.3).
Okay, but the account manager is not enabled by default, right?
This behavior is an artifact of the eggs being activated per Python
interpreter. So if all your projects are running in a single
interpreter, you'll see the project-specific plugins in WebAdmin, but
they'll be disabled in all but the project they were loaded from.
I don't think there's any good way to work around that. One option
for mod_python is to not use TracEnvParentDir, and enable the
PythonInterpPerDirective directive (or similar).
By the way, I notice setuptools...egg is a directory, not a file.
Should it be?
That's okay. Eggs can be either files or directories.
I also noticed my web-root directory had to be write enabled for
the server in order to create a .python-eggs directory! I don't
feel comfortable about that.
See <http://projects.edgewall.com/trac/wiki/
TracPlugins#SettingupthePluginCache>
Cheers,
Chris
--
Christopher Lenz
cmlenz at gmx.de
http://www.cmlenz.net/
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
