explorer should invoke qbzr with same bzr
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Explorer |
Fix Released
|
Medium
|
Gordon Tyler |
Bug Description
I have bzr 2.2.0 installed on my system and bzr.dev branched into my working area. If I invoke bzr-explorer using bzr.dev, when it invokes qbzr commands such as qconfig, it uses the bzr 2.2.0 installed at the system level instead of bzr.dev.
This means that if I am doing combined development on bzr and qbzr, with changes in bzr that the changes in qbzr depend on, I cannot test using bzr-explorer because it will crash. For example, say I have added the mergetools module to bzrlib in bzr.dev, if I reference that from a qbzr command, I can use that qbzr command from the commandline in my working area just fine but if I try to invoke that qbzr command from bzrdev explorer then it fails with an ImportError for the mergetools module.
Relevant section from bzr.log:
Wed 2010-10-06 20:44:23 -0400
0.152 bazaar version: 2.3.0dev2
0.152 bzr arguments: [u'explorer']
0.253 failed to load compiled extension: No module named _static_tuple_c
0.254 failed to load compiled extension: cannot import name _btree_
0.260 looking for plugins in C:/Users/
0.260 looking for plugins in C:\dev\
0.274 encoding stdout as sys.stdout encoding 'cp437'
0.394 failed to load compiled extension: No module named _rio_pyx
0.398 failed to load compiled extension: No module named _dirstate_
0.420 failed to load compiled extension: No module named _known_graph_pyx
0.632 failed to load compiled extension: No module named _bencode_pyx
0.696 loading explorer extensions for clothes [u'Bazaar support', u'Register on Launchpad']
0.754 setting preference toolbar-contents to expanded (was expanded)
0.756 setting preference workingtree-
0.756 setting preference custom-dialogs to true (was true)
0.756 setting preference language to en_US (was en_US)
0.756 setting preference location-
0.806 failed to load compiled extension: No module named _chk_map_pyx
0.823 failed to load compiled extension: No module named _annotator_pyx
0.828 failed to load compiled extension: No module named _knit_load_data_pyx
0.854 failed to load compiled extension: No module named _groupcompress_pyx
4.383 Deprecated function called
Called from:
File "C:\dev\
result = self._lookup_
File "C:\dev\
return command_
File "C:\dev\
return shlex_split_
File "C:\dev\
trace.
Wed 2010-10-06 20:44:27 -0400
0.042 bazaar version: 2.2.0
0.042 bzr arguments: [u'qconfig']
0.075 looking for plugins in C:/Users/
0.075 looking for plugins in C:/Program Files (x86)/Bazaar/
0.076 Plugin name explorer already loaded
0.076 Plugin name qbzr already loaded
0.153 encoding stdout as osutils.
0.204 Traceback (most recent call last):
File "C:\dev\
File "C:\dev\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "C:\dev\
ImportError: cannot import name mergetools
Related branches
- Alexander Belchenko: Approve
- Gary van der Merwe: Approve
-
Diff: 42 lines (+7/-9)1 file modifiedlib/explorer.py (+7/-9)
description: | updated |
description: | updated |
Changed in bzr-explorer: | |
importance: | Undecided → Medium |
milestone: | none → 1.1.2 |
Changed in bzr-explorer: | |
status: | In Progress → Fix Released |
Can you enable debug mode and check the command-line which is used to
launch qconfig?
I'm not quite understand why you have this effect. in lib/explorer.py we executable,
have proper detection of bzr excutable, see method _get_bzr_
and method run_bzr_gui.
My best guess is: some code does not use _get_bzr_executable and just
invokes `bzr qconfig`, which indeed will run your system bzr.