summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCalum Lind <calumlind@gmail.com>2018-10-30 14:20:38 +0000
committerCalum Lind <calumlind@gmail.com>2018-11-02 08:47:57 +0000
commit3433a911ccd7192c37c3cdbcc8094d276a68c705 (patch)
tree5894404253a6a2fa13b777be0dc82d215d8bb665
parent967606fa0f5c3afef783d1fcf08744408f5f71c5 (diff)
downloaddeluge-3433a911ccd7192c37c3cdbcc8094d276a68c705.tar.gz
deluge-3433a911ccd7192c37c3cdbcc8094d276a68c705.tar.bz2
deluge-3433a911ccd7192c37c3cdbcc8094d276a68c705.zip
[Plugins] Allow enabling any plugin Python version
Users encounter issues when trying to install plugins with differing python versions. If the plugin was built with Py2.6 but they are using Py2.7 the plugin would not load. With the move to Python 3 this could become more of an issue. The workaround is to let the plugin manager to try to load the deluge plugin regardless of the python version it was built with. This will put the onus on plugin author to keep the plugin code compatible with more Python versions.
-rw-r--r--deluge/pluginmanagerbase.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/deluge/pluginmanagerbase.py b/deluge/pluginmanagerbase.py
index 0a84c1b1c..b6335d2d9 100644
--- a/deluge/pluginmanagerbase.py
+++ b/deluge/pluginmanagerbase.py
@@ -106,7 +106,7 @@ class PluginManagerBase(object):
pkg_resources.working_set.add_entry(user_plugin_dir)
plugins_dirs.append(user_plugin_dir)
- self.pkg_env = pkg_resources.Environment(plugins_dirs)
+ self.pkg_env = pkg_resources.Environment(plugins_dirs, None)
self.available_plugins = []
for name in self.pkg_env: