lcreeve at rockwellcollins.com ()
2011-08-22 21:14:13 UTC
We have seen an occasionally recurring problem when trying to run omniidl
on Windows XP. On one system it runs fine, and on another we see this
error when omniidl is entered at a command prompt:
'import exceptions' failed; use -v for traceback
Warning! Falling back to string-based exception
'import site' failed; use -v for traceback
Traceback (innermost last):
File "<string>", line 1, in ?
ImportError: No module named os
In both cases the omniORB distribution is identical, and Python27 is
installed. The environment variable OMNIORB_HOME is defined, and the Path
has the following added to it:
%OMNIORB_HOME%\bin\x86_win32
The environment also defines
PYTHONPATH=C:\Python27
Does anyone know what we might be missing?
Thanks,
Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20110822/e3faec35/attachment.htm
on Windows XP. On one system it runs fine, and on another we see this
error when omniidl is entered at a command prompt:
'import exceptions' failed; use -v for traceback
Warning! Falling back to string-based exception
'import site' failed; use -v for traceback
Traceback (innermost last):
File "<string>", line 1, in ?
ImportError: No module named os
In both cases the omniORB distribution is identical, and Python27 is
installed. The environment variable OMNIORB_HOME is defined, and the Path
has the following added to it:
%OMNIORB_HOME%\bin\x86_win32
The environment also defines
PYTHONPATH=C:\Python27
Does anyone know what we might be missing?
Thanks,
Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20110822/e3faec35/attachment.htm