Bjørn Stabell wrote:
> I do remember posting a comment on the Django docs site about
> mod_python and mpm-worker crashes a while ago, but I cannot find it on
> the Django site anymore.
>
> In any case, we were using mod_python 3.1.3-3. I'm happy to hear it's
> been fixed in 3.2.8.
I do remember posting a comment on the Django docs site about
mod_python and mpm-worker crashes a while ago, but I cannot find it on
the Django site anymore.
In any case, we were using mod_python 3.1.3-3. I'm happy to hear it's
been fixed in 3.2.8. Unfortunately, even Debian unstable is still
olive wrote:
> Graham Dumpleton August 17, 2006 at 11:59 p.m.
>
> You really need to provide an explanation of why the worker MPM cannot
> be used and the prefork MPM must be used.
Uhm... I would not say that it 'cannot' be used. It can (after some long
time ago threading issues with db
Malcom,
The context of this comment is
http://www.djangoproject.com/documentation/modpython/#c2029
What I would like to know is if something has been done or will be to
ensure that Django works along with mod_python 3.3.
As far as I understand this will allow us to run any taste of Apache in
On 18 aug 2006, at 15.07, Malcolm Tredinnick wrote:
>
> On Fri, 2006-08-18 at 05:54 -0700, olive wrote:
>> Hi folks,
>>
>> Have you read the following from Django Comments, what do you
>> think of
>> it ?
>
> This seems to be in response to some question. What is the context,
> though? What was
On Fri, 2006-08-18 at 05:54 -0700, olive wrote:
> Hi folks,
>
> Have you read the following from Django Comments, what do you think of
> it ?
This seems to be in response to some question. What is the context,
though? What was the original question and where was this posted? Was
there a
Hi folks,
Have you read the following from Django Comments, what do you think of
it ?
Graham Dumpleton August 17, 2006 at 11:59 p.m.
You really need to provide an explanation of why the worker MPM cannot
be used and the prefork MPM must be used. The reason is that this
doesn't make a lot of
