Re: [Orbit-python-list] Release program for 0.3.1

[Christian R. R. <ki...@as...>]

On 7 Oct 2001, Jason Tackaberry wrote:

> > <zilch> CORBA.ORB_init (sys.argv[], CORBA.ORB_ID, CORBA.TRUE)
>
> Actually as long as the third argument is optional (and it is), then
> it's fine.  We "bend" the spec all over the place in order to provide
> enhancements.  As long as spec-compliant programs work the way they
> should with o-p then it's fine.

If it's not already a problem, I think this could be "bad" if in the
future OMG decides to add a third parameter. I think parameter lists are
the type of thing that can be changed in a standard a lot, specially in
python where we can have optional arguments.

So I'm proposing :-) that we use something like

"from CORBA import use_gtk_mainloop"

Or perhaps something like CORBA._use_gtk_mainloop = 1

Tack, you had a proposal for non-standard extensions. How would they work?

> This stuff isn't suitable for 0.3.x, but maybe 0.4.x, since it's the
> first step to making o-p usable with threads.

Uhm, well I should point out this has nothing to do with threads -
actually, the whole problem is working around threads in pygtk. If we had
thread support no pygtk modifications would be necessary.

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL