failure to lazy-load a plugin repository format should not be fatal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
If we fail to lazy-load something from a registry, we should possibly give a warning rather than a fatal error. In the case below this format is not relevant to the command I'm trying to run.
mbp@grace% bzr info
bbzr: ERROR: exceptions.
Traceback (most recent call last):
File "/usr/lib/
return run_bzr(argv)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
verbose=
File "/usr/lib/
outfile)
File "/usr/lib/
format = describe_
File "/usr/lib/
format = bzrdir.
File "/usr/lib/
return self.get(key)()
File "/usr/lib/
bd.
File "/usr/lib/
raise ImportError('failed to load %s: %s' % (full_name, e))
ImportError: failed to load bzrlib.
bzr 1.6b3 on python 2.5.2 (linux2)
arguments: ['/usr/bin/bzr', 'info']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_AU.UTF-8'
plugins:
bzrtools /usr/lib/
groupcompress /home/mbp/
gtk /home/mbp/
launchpad /usr/lib/
loom /home/mbp/
pqm /home/mbp/
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
Changed in bzr: | |
importance: | Undecided → Low |
Changed in bzr: | |
status: | Triaged → Confirmed |
tags: | added: check-for-breezy |
tags: |
added: format-infrastructure formats removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Low |
I agree, though as these are development formats, I don't think it is critical to fix this yet.