bzrlib.plugin.load_plugins() loads system plugins even for non-system bzrlib
Bug #316192 reported by
Michael Hudson-Doyle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Vincent Ladeuil | ||
Launchpad itself |
Fix Released
|
High
|
Tim Penhey |
Bug Description
Lauchpad uses our own branch of bzrlib, which is not quite up to date with bzr.dev currently. I have bzr installed from the nightly ppa. If I try to run our bzr executable, I get a message about a new plugin in the system location:
mwh@grond:trunk$ ./sourcecode/
'module' object has no attribute 'CredentialStore'
Unable to load plugin 'netrc_
It sure does!
Its definitely unfortunate that a system plugin can cause problems for my separate install of bzrlib.
Even setting BZR_PLUGIN_PATH doesn't help.
Related branches
lp:~bzr/bzr/412930-plugin-path
- John A Meinel: Approve
- Diff: 535 lines
lp:~vila/bzr/integration
- Vincent Ladeuil: Approve
-
Diff: 31 lines (+4/-4)2 files modifiedbzrlib/lazy_regex.py (+3/-3)
doc/en/release-notes/bzr-2.7.txt (+1/-1)
Changed in launchpad-bazaar: | |
status: | In Progress → Fix Committed |
Changed in launchpad-bazaar: | |
status: | Fix Committed → Fix Released |
Changed in bzr: | |
milestone: | none → 2.1 |
status: | Fix Committed → Fix Released |
Changed in bzr: | |
milestone: | 2.1.0 → 2.1b1 |
To post a comment you must log in.
I think there are two issues:
BZR_PLUGIN_PATH should override completely (perhaps with some magic
element to say 'the default path here').
And we shouldn't use the python path for an uninstalled bzr. We should
use it if bzr is installed, just not when running from a source dir.
-Rob