[pylucene-dev] status of pylucene & mod_python

[Ofer Nave]

> -----Original Message-----
> From: pylucene-dev-bounces at osafoundation.org 
> [mailto:pylucene-dev-bounces at osafoundation.org] On Behalf Of Ofer Nave
> Sent: Monday, March 26, 2007 2:22 AM
> To: pylucene-dev at osafoundation.org
> Subject: RE: [pylucene-dev] status of pylucene & mod_python
> 
> I just finished coding up a module I named ipc.py.  It 
> provides a function called call_in_seperate_process that 
> takes a module name, a function name, and wildcard args.  It 
> then uses popen2.Popen3 to invoke the ipc module as an 
> executable, and yaml to serialize the request and the args.  
> The ipc module-as-executable deserializes the request, 
> executes it, uses yaml to serialize the output of the 
> function, and prints it to STDOUT, where it is then 
> deserialized by the parent process and returned.

I promise I won't innundate this list with bug fixes and improvements to my
ipc.py module - after this one.  :)

Just found a critical bug.  If you care to use my ipc.py module, first
replace line 9:

ME = os.path.realpath(__file__)

with this:

ME = os.path.realpath(__file__).rstrip('c')  # rstrip necessary because if
module has been compiled, the compiled file will be return by __file__
('ipc.pyc')

-ofer