Changes between Version 45 and Version 46 of TracPlugins

Timestamp:

Feb 4, 2008, 7:46:40 PM (16 years ago)

Author:

osimons

Comment:

Updating some information on plugin loading (ref. #6468), and also added some information about uninstalling plugins.

TracPlugins

@@ -34 +34 @@
 Once you have the plugin archive, you need to copy it into the `plugins` directory of the [wiki:TracEnvironment project environment]. Also, make sure that the web server has sufficient permissions to read the plugin egg.
 
+To uninstall a plugin installed this way, remove the egg from `plugins` directory and restart web server.
+
 Note that the Python version that the egg is built with must
 match the Python version with which Trac is run.  If for
@@ -39 +41 @@
 upgraded your standalone Python to 2.4, the eggs won't be
 recognized.
+
+Note also that in a multi-project setup, a pool of Python interpreter instances will be dynamically allocated to projects based on need, and since plugins occupy a place in Python's module system, the first version of any given plugin to be loaded will be used for all the projects. In other words, you cannot use different versions of a single plugin in two projects of a multi-project setup. It may be safer to install plugins for all projects (see below) and then enable them selectively on a project-by-project basis.
 
 === For All Projects ===
@@ -76 +80 @@
 
 Note: After installing the plugin, you need to restart your web server.
+
+==== Uninstalling ====
+
+`easy_install` or `python setup.py` does not have an uninstall feature. Hower, it is usually quite trivial to remove a globally installed egg and reference:
+ 1. Delete the .egg file or folder from where it is installed, usually inside `$PYTHONLIB/site-packages/`.
+ 1. Edit the `$PYTHONLIB/site-packages/easy-install.pth` text file and delete the line that contains the reference to the removed egg.
+ 1. Restart web server.
+
+If you are uncertain about the location of the egg, here is a small tip to help locate an egg (or any package) - replace `myplugin` with whatever namespace the plugin uses (as used when enabling the plugin):
+{{{
+>>> import myplugin
+>>> print myplugin.__file__
+/opt/local/python24/lib/site-packages/myplugin-0.4.2-py2.4.egg/myplugin/__init__.pyc
+}}}
 
 == Setting up the Plugin Cache ==