could please ping me when/if you
think we're ready for the core group vote and we have a tally.
Thanks!
Grisha
-- Forwarded message --
Date: Sat, 01 Jul 2006 23:18:05 -0400
From: Jorey Bump [EMAIL PROTECTED]
To: python-dev@httpd.apache.org
Subject: Re: mod_python 3.2.9
.
Thanks!
Grisha
-- Forwarded message --
Date: Sat, 01 Jul 2006 23:18:05 -0400
From: Jorey Bump [EMAIL PROTECTED]
To: python-dev@httpd.apache.org
Subject: Re: mod_python 3.2.9 available for testing
+1 Linux Slackware 10.2, Apache 2.0.55 (mpm-prefork
: Re: mod_python 3.2.9 available for testing
+1 Linux Slackware 10.2, Apache 2.0.55 (mpm-prefork), Python 2.4.1
Jim Gallacher wrote:
The mod_python 3.2.9 tarball is available for testing.
This tarball is unchanged from 3.2.9-rc3, but should be retested
anyway
- just in case something went pair
+1 MacOSX 10.4.6 PPC, Apache-2.0.55 (mpm/worker), Python-2.3.5
+1 MacOSX 10.4.6 PPC, Apache-2.2.1 (mpm/worker), Python-2.3.5
On 30/06/2006, at 12:52 PM, Jim Gallacher wrote:
The mod_python 3.2.9 tarball is available for testing.
This tarball is unchanged from 3.2.9-rc3, but should be retested
I've got :+1 Windows XP SP2, Apache 2.0.58 (mpm_winnt), Python 2.4.3But, and it's my fault for not having tested this for a long time :-1 Windows XP SP2, Apache 2.2.2 (mpm_winnt), Python 2.4.3
Only two tests fail but with a segfault, it's test_srv_register_cleanup and test_apache_register_cleanup.
+1 Fedora Core 5 (i386), Apache 2.2.0 (mpm-prefork), Python 2.4.3
The mod_python 3.2.9 tarball is available for testing.
This tarball is unchanged from 3.2.9-rc3, but should be retested anyway
- just in case something went pair-shaped in the process of tagging and
packaging.
Here are the rules:
In order for a file to be officially announced, it has to be
+1 Linux Debian Sid, Apache 2.0.55 (mpm-worker), Python 2.3.5
Jim Gallacher wrote:
The mod_python 3.2.9 tarball is available for testing.
This tarball is unchanged from 3.2.9-rc3, but should be retested anyway
- just in case something went pair-shaped in the process of tagging and