OK, I found the problem. The LockFile line is commented out in test.py
which causes Apache to try to create the lock in the default location in
/var/run.
http://svn.apache.org/viewcvs.cgi/httpd/mod_python/trunk/test/test.py?rev=125771r1=106619r2=125771
So the question is - can we just put
I'd keep the patch nonetheless - I think this is how it should be.
Grisha
On Mon, 12 Sep 2005, Jim Gallacher wrote:
-1 for this patch. Actually, the patch itself is fine - it just doesn't fix
the problem. The unit tests are still failings as per my previous messages.
ie the following is
Done. All tests pass on my FreeBSD box. Nicolas - can you test Win32, I'm
not 100% sure if the change to test.py I made will work.
Grisha
On Tue, 13 Sep 2005, Nicolas Lehuen wrote:
Yes, now I remember I had to comment this line out because it broke
something on Win32. Go ahead, uncomment
Gregory (Grisha) Trubetskoy wrote:
Done. All tests pass on my FreeBSD box. Nicolas - can you test Win32,
I'm not 100% sure if the change to test.py I made will work.
Good news. If the changes can be checked in and Nicolas can give a +1 on
the Windows test then I'll be able to generate the
Alright, cool. So I guess we're ready to roll the next tarfile now.
Grisha
On Tue, 13 Sep 2005, Nicolas Lehuen wrote:
I'm sure it is required, even after fixing the S in APR_HAS_THREADS I tried
with and without the PyEval_AcquireLock code and the latter works while the
former doesn't. I
A new mod_python 3.2.2 beta tarball is now available for testing.
Hopefully this will be the last beta before the official 3.2 release.
Here are the rules:
In order for a file to be officially announced, it has to be tested by
developers on the dev list. Anyone subscribed to this list can (and
+1 (slightly patched for Apache 2.1.x)
Slackware Linux 10.1
gcc version 3.3.4
Python 2.4.1
Apache 2.1.6 Alpha
Jim Gallacher wrote:
A new mod_python 3.2.2 beta tarball is now available for testing.
Hopefully this will be the last beta before the official 3.2 release.
Here are the rules:
In