| 2010-10-07 01:17:28 |
Gordon Tyler |
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, if 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. |
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.
|
|
| 2010-10-07 01:18:26 |
Gordon Tyler |
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.
|
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_serializer_pyx
0.260 looking for plugins in C:/Users/Owner/AppData/Roaming/bazaar/2.0/plugins
0.260 looking for plugins in C:\dev\bzr\mergetools\bzrlib\plugins
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_helpers_pyx
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-default-to-edit to True (was True)
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-selector-style to tree (was tree)
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\bzr-explorer\trunk\lib\app_suite.py", line 120, in lookup
result = self._lookup_here(cmd_id, context, location_type)
File "C:\dev\bzr-explorer\trunk\lib\app_suite.py", line 138, in _lookup_here
return command_to_args(result, context)
File "C:\dev\bzr-explorer\trunk\lib\app_suite.py", line 150, in command_to_args
return shlex_split_unicode(command_to_expanded(template, context))
File "C:\dev\bzr\mergetools\bzrlib\symbol_versioning.py", line 98, in decorated_function
trace.mutter_callsite(4, "Deprecated function called")
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/Owner/AppData/Roaming/bazaar/2.0/plugins
0.075 looking for plugins in C:/Program Files (x86)/Bazaar/plugins
0.076 Plugin name explorer already loaded
0.076 Plugin name qbzr already loaded
0.153 encoding stdout as osutils.get_user_encoding() 'cp1252'
0.204 Traceback (most recent call last):
File "C:\dev\qbzr\mergetools\lib\commands.py", line 166, in run
File "C:\dev\qbzr\mergetools\lib\commands.py", line 504, in _qbzr_run
File "bzrlib\lazy_import.pyo", line 122, in __call__
File "bzrlib\lazy_import.pyo", line 89, in _replace
File "bzrlib\lazy_import.pyo", line 192, in _import
File "C:\dev\qbzr\mergetools\lib\config.py", line 27, in <module>
ImportError: cannot import name mergetools |
|
