[omniORB] omniidl on Windows 9X

[Mair Quentin]

Duncan,

Thanks for that.

A quick workaround (tried on ME):

copy _sre.lib into the same dir as the example. Use the "-T" option -
everything works OK.

Still looks like an environment variable as omniidl can't find
the Python DLLs. Does anybody know what I should set?


Cheers,


Q

PS Interestingly the below worked before copying _sre.lib over. Is it
because omniidl is an exe? (I'm fairly new to python and haven't looked at
how to build exes from scripts):


C:\omni\examples\echo>type retest.py
import re, sre_compile, _sre

print dir(re)
print dir(sre_compile)
print dir(_sre)


C:\omni\examples\echo>python retest.py
['DOTALL', 'I', 'IGNORECASE', 'L', 'LOCALE', 'M', 'MULTILINE', 'S',
'Scanner', '
T', 'TEMPLATE', 'U', 'UNICODE', 'VERBOSE', 'X', '__builtins__', '__doc__',
'__fi
le__', '__name__', 'compile', 'copy_reg', 'engine', 'error', 'escape',
'findall'
.	.
.	.
.	.
<rest of output OK>


> -----Original Message-----
> From: Duncan Grisby [mailto:dgrisby@uk.research.att.com]
> Sent: 14 May 2001 10:46
> To: Mair Quentin
> Cc: omniorb-list@uk.research.att.com
> Subject: Re: [omniORB] omniidl on Windows 9X 
> 
> 
> On Monday 14 May, Mair Quentin wrote:
> 
> > How do you get onniidl (from OnmiORBpy 1.3 for Python 2.0) 
> to work on
> > Windows98SE/ME? On both boxes I get:-
> > 
> > C:\omni\examples\echo>omniidl -T -bpython echo.idl
> > omniidl: Could not import back-end `python'
> > omniidl: Maybe you need to use the -p option?
> > omniidl: (The error was `No module named _sre')
> > 
> > C:\omni\examples\echo>
> > 
> > Using or not using "-T" makes no difference. Using "-p" 
> (not shown) also
> > makes no difference. Also I have no problem running 
> (non-CORBA) python
> > scripts
> 
> How odd. It's failing when it tries to import re, the regular
> expression module. What happens if you try to "import re" from a
> Python prompt?  If that fails, your Python installation is broken for
> some reason. If it works, something very odd is going on with
> omniidl. One thing to try is to set the environment variable
> PYTHONVERBOSE to 1. That will print out a huge amount of stuff about
> what Python is doing, which might help.
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --
>