[omniORB] _omnipy load problem

[Duncan Grisby]

On Saturday 29 December, charles bartlett wrote:

> Attempting to run echo example.
> 
> Unzipped omniORBpy-3.1-x86-win32-python2.5.zip and
> omniORB-4.1.1-x86-win32-vc8.zip to windows box with python 2.5.1 loaded.
> 
> in python, attempt: "import omniORB"
> 
> error message - "import _omnipy
> ImportError: DLL load failed: The specified module could not be found."
> 
> sys.path includes the directory containing _omnipy; the error message is
> misleading - _omnipy is apparently found but can't be read.

To use omniORBpy, you _just_ need omniORBpy-3.1-x86-win32-python2.5.zip
You should not use the omniORB 4.1.1 distribution at all. If you do
install it, you must put it somewhere unrelated and make sure it is not
on your path.

It sounds like you need to put the omniORBpy binary directory on your
path. Add ...\omniORBpy-3.1\bin\x86_win32 to your path. The _omnipy
module is linked against the omniORB library, and that's what can't be
found.

You are right that the error message is misleading, but it's a message
from Python itself, so omniORBpy can't do anything about it.

> Noted <many> similar problems reported in mail; fix answers refer to
> incompatible versions of omniORB and python; in my case, should not be
> incompatible.

The similar problem that other people have is that they get conflicts
when running omniidl. That is due to mixing bits of the omniORB binary
distribution with bits of the omniORBpy distribution. The omniORB
distribution contains a minimal version of Python 1.5.2 which conflicts
with newer versions when used with omniORBpy.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --