[Orbit-python-list] Where are the constants?

[Will D. <Wil...@as...>]

Dear orbit-python experts,

I'm new to python and new to orbit-python and heve the following simple
problem.
Given the simple.idl:

--- simple.idl -------

module M {
  interface my_I {
    const long my_const = 3;

    struct my_struct {
      long my_member[my_const];
    };

    long my_func
    (
       out my_struct my_out
    );
  };
};

--- end of simple.idl -------

Given the following session:

wsasd649:~ % python
Python 2.2.1 (#1, Sep 12 2002, 16:24:44) 
[GCC 3.1.1] on sunos5
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys,ORBit
>>> ORBit.load_file("simple.idl")
>>> dir()
['ORBit', '__builtins__', '__doc__', '__name__', 'sys']
>>> import M
>>> dir()
['M', 'ORBit', '__builtins__', '__doc__', '__name__', 'sys']
>>> dir(M)
['__doc__', '__name__', 'my_I']
>>> dir(M.my_I)
['__class__', '__cmp__', '__delattr__', '__doc__', '__getattribute__',
'__getstate__', '__hash__', '__init__', '__module__', '__new__',
'__reduce__', '__repr__', '__setattr__', '__slots__', '__str__',
'__typecode__', '_duplicate', '_hash', '_is_a', '_is_equivalent',
'_is_nil', '_narrow', '_non_existent', 'my_func', 'my_struct']
>>> 

I can find import module M and its content M.my_I, M.my_I.my_struct, and
M.my_I.my_func.

I havegot the following questions:
- WHERE has my_const gone? How can i access it?
- Do I need another import?
- Could there be placed an example on the internet that shows
  a simple idl and how to access its content within python.
- I know there are two freeware ORBit python bindings: pyORBit and
ORBit-python
  which one is the most mature, and why should I use it?

PS:  I am using pyORBit for the ORBit python binding 

Thanks in advance,

Will Denissen.


-- 
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.