[omniORB] omniORBpy: order of import statements

[Duncan Grisby]

On Sunday 9 December, Christof Meerwald wrote:

[...]
> and then import the module N before module M into my Python script, the
> Python module M doesn't contain all the expected elements:

[...]
> I guess the problem is that b_idl imports a_idl and creates the "M" module
> in Python. The "import M" then has no effect because Python thinks it has
> already imported the "M" module and therefore c_idl never gets imported.

That is indeed the problem. I think this has come up before. I can't
think of a clean way to avoid it. If you can, let me know. :-)

The work-around to be sure that a particular IDL file's definitions
have been imported is to import the c_idl module explicitly.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --