plugins installed as eggs are not found by bzrlib
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
In buildout environments (similar to virtualenv ones) packages are installed as separate eggs; so the path on disk for (say) bzr-loom is *not* path-to-
setuptools provides an API to introspect the active eggs, which can report on the packages and paths available, which could be used by bzr to find these plugins and let them be imported.
We would like to do this for Launchpad, to more easily use releases of bzr plugins.
Doing the introspection may be slow; we would be happy for a special option to be set to tell bzrlib to do it.
Also we have a situation where we control which plugins are loaded where, some of the time - we may end up coming up with a filtering patch to support that, once the base code can find these eggs at all (I mention it now for completeness alone).
