Re: Re: [pygtk] Conflicting omniORBpy and PyORBit

On Friday 15 August, James Henstridge wrote:

> OmniORB does something similar, although I don't know if the CORBA 
> module name gets bound when you import OmniORB.

It doesn't, but it would be easy to make it do so if that was the
agreed thing to do.

> The question is whether (a) should any ORB provide a toplevel CORBA 
> module you can import without any other imports, and (b) whether this 
> behaviour should be clarified in the spec.

It would break an enormous amount of code using omniORB to remove the
top-level CORBA module, so I don't think that's a sensible option.

This is really only an issue for packagers like RedHat and Debian. In
any other setting, users can choose to install multiple ORBs in
different places, and choose the right one with PYTHONPATH. This
problem only requires if you have a reason to install them in the same
place.

The Python mapping spec is (was?) mainly looked after by Martin von
Loewis. Are you listening Martin?

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@xxxxxxxxxx     --
   -- http://www.grisby.org --

_______________________________________________
omniORB-list mailing list
omniORB-list@xxxxxxxxxxxxxxxxxxx
http://www.omniorb-support.com/mailman/listinfo/omniorb-list