Re: [Orbit-python-list] hi

[Jason T. <ta...@li...>]

> First I would like to point out that it seems like it is dead quiet on
> this list ( im not subscribed ) atleast if you like at the archive.

Yup, life here has been fairly quiet.  I really wanted to make another
release early September, but my RL job has been occupying quite a bit of
my time and I need to do a few hours more hacking before it is ready.

> the output looks like this.
> <CORBA.Object object at 80ff980> 
> 
> Could one take that it is a nil reference with orbit-python ( Id like a
>  is_nil implemented ) or should it be None ? 

According to the mapping specification, Nil objects are represented by
None.  I don't think ORBit-Python handles this properly, now that you
mention it.  And so it is on the todo list of things to check.

> So ofcourse the client i wrote with orbit-python does not
> work, the c++ client works, but anyway I would like to know what
> makes 't' to be a CORBA.Object.

If the object is a CORBA.Object it means that the interface definition
for the object represented in the IOR was not found.  It looks like you
are importing the idl before doing anything, so this could very well be
a bug.  Try printing the __repo_id attribute of that object and see what
you get.  If it's correct, then the problem would seem to be the dynamic
IDL loading.  Can you send me the IOR and IDL files you're working with?

Also, give the CVS version a try, as this may inadvertently have been
fixed.  (There's been quite a bit of internal changes since the last
release.)  You'll have to patch automake as documented in the
python-am-changes directory.

Cheers,
Jason.