Hi Graham,
After a few interesting weeks, I finally manage to get some time to
help on mod_python.
I've ran the tests on the latest Subversion revision (407968) with
Apache 2.0.58 and Python 2.4.3, and all test pass, including the SSI
ones.
For a yet unknown reason, every test fail with a debug
I've forgot to mention the platform : as usual for me, it's Windows XP SP2.
Regards,
Nicolas
2006/5/20, Nicolas Lehuen <[EMAIL PROTECTED]>:
Hi Graham,
After a few interesting weeks, I finally manage to get some time to
help on mod_python.
I've ran the tests on the latest Subversion revision (
OK, it seems that my last hypothesis was the good one : mod_python is
doing things with thread states that are frowned upon by debug build.
The tests are only performed in the debug build, so that's why we had
no problem with the release build.
The tests are found in pystate.c, in function PyThre
On 20/05/2006, at 6:27 PM, Nicolas Lehuen wrote:
OK, it seems that my last hypothesis was the good one : mod_python is
doing things with thread states that are frowned upon by debug build.
The tests are only performed in the debug build, so that's why we had
no problem with the release build.
Graham,
In fact PyEval_AcquireThread does call PyThreadState_Swap :
void
PyEval_AcquireThread(PyThreadState *tstate)
{
if (tstate == NULL)
Py_FatalError("PyEval_AcquireThread: NULL new thread state");
/* Check someone has called PyEval_InitThreads() to create the
I can help test mod_python if needed. I run on FreeBSD 6 with Python 2.4.3
I've got the trunk checked out and built and can submit "make check"
results when appropriate/helpful.
--
Jeff Hinrichs
Dundee Media & Technology, Inc
[EMAIL PROTECTED]
Jeff Hinrichs - DM&T wrote:
I can help test mod_python if needed. I run on FreeBSD 6 with Python 2.4.3
I've got the trunk checked out and built and can submit "make check"
results when appropriate/helpful.
Hi Jeff,
Test away. :) I don't think the development trunk has been given a
workout on
I used pylint to assist in cleaning up the indentation mess in util.py.
I ended up checking all our lib/python/mod_python/*.py code, and
needless to say the results were edifying. The output is rather
extensive, with a lot noise regarding missing docstrings and the like,
but I suspect combi
mod_python 3.2.x branch built, installed and tested (python test.py)
succesfully on
FreeBSD lakota.dundeemt.pri 6.0-RELEASE-p6 FreeBSD 6.0-RELEASE-p6 #0:
Wed Apr 5 23:27:07 CDT 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
I did receive the following warning during the test:
Starti
FreeBSD 6
Python 2.4.3
==
FAIL: test_phase_status (__main__.PerRequestTestCase)
--
Traceback (most recent call last):
File "test.py", line 2127, in test_phase_s
For this particular failure, can you look in test/logs/error_log and
find section
which has:
[Mon May 08 21:58:55 2006] [error] phase_status_1
[Mon May 08 21:58:55 2006] [error] phase_status_2
[Mon May 08 21:58:55 2006] [error] phase_status_4
[Mon May 08 21:58:55 2006] [error] phase_status_5
[M
me culpa, forgot to CC the group
-- Forwarded message --
From: Jeff Hinrichs - DM&T <[EMAIL PROTECTED]>
Date: May 21, 2006 1:17 AM
Subject: Re: mod_python trunk fails
To: Graham Dumpleton <[EMAIL PROTECTED]>
Graham,
apache-2.2.2
Here are the only lines that had the phrase "phas
12 matches
Mail list logo