Hi all. I'm one of the Twisted upstream developers, and I thought I'd give some context.
So, this change was intentional. It was done in revision 20920 and fixes bug #2339 in our tracker. It's got a thorough log message: """ Add a function, twisted.plugin.pluginPackagePaths, which returns a list of additional directories to search for plugin modules for a particular plugin package. Change twisted.plugins.__init__ to use this function instead of looping over sys.path directly. Unlike the loop previously in twisted.plugins.__init__, pluginPackagePaths will not include any directory which is a Python package. This prevents plugins from being discovered from packages which Python may not actually be able to import and limits plugin discovery to those installed on the version of the package which is in use by an application. It also allows a site installation to co-exist with another installation (for example, a personal user installation) without interfering with each other. """ The way we expect users to use the Twisted plugin system is by installing their plugin files into _the_ main twisted plugins directory, at site-packages/twisted/plugins, and that's what we've always intended. This is not necessarily as far as we'll go, though; new features which allow users to (explicitly) specify additional plugin directories are certainly a possibility. However, It's unfortunate that we've introduced a backwards incompatibility in this case; we did not foresee this kind of directory setup. I can't offer opinions as to in which direction this should be resolved. I can think of a workaround for this issue in python-twisted: for example, by patching __init__.py to explicitly include the python-support twisted/plugins dircetory in __path__. python-nevow could also be updated. I'm going to talk to some other Twisted developers to see what they think about this. -- Christopher Armstrong International Man of Twistery http://radix.twistedmatrix.com/ http://twistedmatrix.com/ http://canonical.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
