omniORB for Python
This is version 1.4 of omniORBpy, a complete CORBA ORB for Python.
omniORBpy is copyright AT&T Laboratories - Cambridge. It is free software. The programs in omniORBpy are distributed under the GNU General Public Licence as published by the Free Software Foundation. See the file COPYING for copying permission of these programs. The libraries in omniORBpy are distributed under the GNU Library General Public Licence. See the file COPYING.LIB for copying permission of these libraries.
We run omniORBpy on Linux, Solaris, Irix, HPUX, and Windows NT. It has already been ported to a number of other operating systems. It should be easy to port to any other platform for which omniORB and Python are available.
omniORBpy follows the official OMG CORBA to Python mapping, available from http://cgi.omg.org/cgi-bin/doc?formal/01-02-66.
For more details about what is and is not supported in omniORBpy, see the release notes. The ORB runtime uses a Python extension module written in C++ to talk to the rest of omniORB, but the stubs generated from IDL are pure Python.
omniORBpy can use either omniORB 3.0 or omniORB 2.8. If you use omniORB 3.0, the full POA facilities are available from Python; if you use 2.8, many POA operations are not supported.
omniORBpy requires Python version 1.5.2 or later, which you can get from www.python.org.
BugsFor a list of bugs which have been fixed since the 1.4 release, see this page.
You may also find the other omniORB documentation useful.
The following binary distributions are available. They contain the omniORBpy 1.4 and omniORB 3.0.4 runtime libraries and the omniORBpy Python source. They do not contain the omniORBpy C++ source. If you redistribute these binary distributions, you must also distribute the omniORB and omniORBpy source packages, to comply with the terms of the GNU public licenses.
For Python 2.1
For Python 1.5.2
The omniORBpy source distribution must be installed inside the
Alternatively, download the source tarball.
You must first configure and build the main omniORB tree if you haven't already done so (see the README files for details). Then, go to the
CVS branches and tagsThe following branches and tags exist in the
For comments, feedback, etc, please see the 'Keeping in touch' page.