Gustavo J. A. M. Carneiro skrev:
On Ter, 2006-09-26 at 11:01 +0100, Magnus Therning wrote:
I copy-pasted your code into three files here and noticed the same
behaviour. I then went to the PyORBit doc I keep around [1] and tried
the Account example. I got that to work by moving the "import CORBA" to
after the call to "ORBit.load_file". So there shouldn't be something
inherently preventing you from using attributes.
You should always import ORBit before CORBA is imported for the first
time. The reason is that "import CORBA" first just imports whatever the
default ORB in your system is.. could be omniorb or something like that.
If you import ORBit first, pyorbit then provides its own replacement
CORBA module.
Sounds like a good idea to assert that a CORBA module is not imported when
importing ORBit, to avoid loading another orb by mistake.
Johan
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
