OMNIORB - OmniORBpy- Python

[Birgit Rahm]

Thank you.

I use omniORBpy 1.3 because it is the only one I found which works together
with Python 2.0. It is restricted to me to use Python 2.0 and not a higher
Python version. If there is a newer version of omniORBpy working together
with Python 2.0 please tell me.

to the sample:
it is the sample in the omniORBpy intsallation, I think it had to be working
with this version.
The client found the ORB and a object, but this object does not have the
expected variable. Should I take some arguments to the program start? And
which? There is no detailed description or documentation for the samples.

I hope there is anyone who can help.
Birgit

"Duncan Grisby" <duncan-news at grisby.org> schrieb im Newsbeitrag
news:NuKwa.5290$Mu3.95849 at newsfep4-glfd.server.ntli.net...
> In article <b9vekt$4ob$01$1 at news.t-online.com>,
>  Birgit Rahm <br_y at yahoo.de> wrote:
>
> >I try to connect python 2.0 program via omniorb 1.3 to omniorb 3.0. Thats
> >the goal.
> >I am not sure if OMNIORB 3.05 is the same as OMNIORB 3.0 mentioned in the
> >readme.
>
> omniORBpy 1.3 is now very old. You should use version 2.1, in
> conjunction with omniORB 4.0.1. omniORB 3.0 refers to all versions of
> 3.0.x; 3.0.5 is the most recent in that branch.
>
> >Second: I try the sample "wheater" from OMNIORBpy (1.3 to Python 2.0).
First
> >I made with the omniidl a new file, but running this file with python
(not
> >pythonwin) gives me the error "variable not defined: __file_" .
> >Can anyone tell me, which steps I have to do?
>
> Get up to date versions of everything for a start. Try again, and if
> it still doesn't work, post the complete error message you receive.
>
> Cheers,
>
> Duncan.
>
> --
>  -- Duncan Grisby         --
>   -- duncan at grisby.org     --
>    -- http://www.grisby.org --