Merge lp:~mars/tarmac/fix-plugin-import into lp:tarmac
Proposed by
Māris Fogels
Status: | Rejected |
---|---|
Rejected by: | Paul Hummer |
Proposed branch: | lp:~mars/tarmac/fix-plugin-import |
Merge into: | lp:tarmac |
Diff against target: |
29 lines (+5/-1) 1 file modified
tarmac/plugin.py (+5/-1) |
To merge this branch: | bzr merge lp:~mars/tarmac/fix-plugin-import |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Paul Hummer | Disapprove | ||
Review via email: mp+42954@code.launchpad.net |
Description of the change
Hi,
This branch presents a quick and dirty fix to the Tarmac plugin activation code. It adds the Tarmac plugin directories to the system path so that Tarmac can import the plugins.
There may be a better way to do this, but I am leaving that better implementation for someone else to tackle. The code passed manual testing on my local system.
Maris
To post a comment you must log in.
So, the idea here was to create a similar environment to the way bzr imports its plugins (from bzrlib.plugins import whatever). This patch breaks that idea. I think we need to dig deeper into the bzrlib plugin registration code to see why this is not working (I'm pretty sure it worked at some point, so maybe we broke it).
I appreciate that you've found the bug, and that you've proposed a fix. I think this breaks the api we want to use (even though that API is broken as well), so I'm not sure this is the correct way to do this.