[omniORB] Python3.5 support

[Alessandro Pischedda]

Hi Brian,
thank you for the answer. I've copied the directory of the auto-generated
Python code on the project's directory which uses it. Anyway the path
generated from the omniidl is not supported by the Python3.5 which want
absolute path and in fact it return ImportError about the code
auto-generated. Maybe I can try to add the directory to the PYTHONPATH too.

2015-12-10 17:29 GMT+01:00 Brian Neal <bgneal at gmail.com>:

> --------- Forwarded message ----------
> > From: Alessandro Pischedda <alessandro.pischedda at gmail.com>
> > To: omniorb-list at omniorb-support.com
> > Cc:
> > Date: Thu, 10 Dec 2015 15:57:26 +0100
> > Subject: Python3.5 support
> > Hi,
> > I see that OmniOrbpy 4.2 should supports Python3.5 but I've tried to
> compile a .idl with omniidl on a virtual enviroment with, just Python3.5,
> but I've many import error when I try to use the idl compiled. The command
> that I use is
> >
> >     omniidl -bpython <file.idl>
> >
> > I should use something different ? Maybe some option that I forget or
> other ?
> >
> > Thank you
> >
> > P.S. I've tried even to modify the 'import path' on the files but it is
> really tedious and difficult.
> >
>
> I'm not exactly sure what you mean, but after omniidl creates the
> auto-generated Python code, you should treat it just like any other
> 3rd party library. This usually means putting the directory on your
> PYTHONPATH, or copying it to a directory already on that path. You
> should then be able to import it.
>



-- 

Always code as if the guy who ends up maintaining your code will be a
violent psychopath who knows where you live. - *Martin Golding*

There are 10 kind of people. Those who understand binary, and those who do
not. I hate both of them. - *Me*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20151210/ab1236fd/attachment.html>