I think it would be spurious for run_bzr to *not* load plugins by default, it would be being different for difference sake.
IMO run_bzr should honour --no-plugins for folk writing tests that care - but the vast bulk of tests should work with plugins loaded or not.
Perhaps the command line should parameterise this though, so with --no-plugins, run_bzr won't load plugins, otherwise it will.
As a library user the default would then be the same as bzrlib's loading of plugins - e.g. off.
-Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
I think it would be spurious for run_bzr to *not* load plugins by
default, it would be being different for difference sake.
IMO run_bzr should honour --no-plugins for folk writing tests that care
- but the vast bulk of tests should work with plugins loaded or not.
Perhaps the command line should parameterise this though, so with
--no-plugins, run_bzr won't load plugins, otherwise it will.
As a library user the default would then be the same as bzrlib's loading
of plugins - e.g. off.
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://