[mod_python] apache.py

Thanks, will do.


On Thu, 2002-01-10 at 16:51, Ole Hansen wrote:
> Hi,
> 
> I had the very same problem, and for a while I thought I was the only 
> one in the universe. I also made similar hack.
> 
> This is a bug in python itself. The bug was introduced somewhere between 
> Python 2.0 and 2.1.1 and fixed in Python 2.2b3, but Python 2.2 (final) 
> has been released now, so I would go for the final Python 2.2.
> 
> Happy coding :-)
> 
> Br,
> Ole Hansen
> 
> 
> 
> Chuck Lima wrote:
> 
> > Hello,
> > 
> > I may be a little late to the game on this one, but here goes.
> > 
> > python 2.1
> > apache 1.3.22
> > mod_python 2.7.6
> > 
> > Lines 356 and 359 of apache.py were hacking off the "y" from my modules
> > i.e.: "mymodule.py"  was not found because apache.py was looking for
> > "mymodule.p".  It seems the intention was to avoid loading compiled
> > modules.  mod_pyton has never compiled my modules -- is this not
> > standard?
> > 
> > 
> > Changes I made - -
> > 
> > original 356:
> > if os.path.exists(filepath[:-1]) :
> > 
> > new 356:
> > if os.path.exists(filepath) :
> > 
> > Also, "filepath[:-1]" on line 359 was changed to "filepath".
> > 
> > This seems to have solved the problem without adversely affecting the
> > running of my scripts.
> > 
> > 
> > The really odd thing, though; is that I've got another system running
> > the (practically) same setup with no mods.  The difference being the
> > apache version.
> > 
> > no mods here:
> > python 2.1
> > apache 1.3.19
> > mod_python 2.7.6
> > 
> > Comments, please.
> > 
> > Thanks,
> > -Chuck
> > 
> > _______________________________________________
> > Mod_python mailing list
> > Mod_python at modpython.org
> > http://www.modpython.org/mailman/listinfo/mod_python
> > 
> > .
> > 
> > 
> 
> 
> 
>