You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_python-dev@quetz.apache.org by Jim Gallacher <jp...@jgassociates.ca> on 2006/03/22 05:16:20 UTC
mod_python 3.3.0-dev-20060321 available for testing
mod_python-3.3.0-dev-20060321 is available for testing.
We are asking the mod_python development community for assistance in
testing the current development branch. Hopefully this will allow us to
catch new bugs or regressions early, and when we are ready for the next
release the beta cycle will be much shorter.
This snapshot addresses 33 issues since 3.2.7 was released, including
apache 2.2 support and the introduction of a new module importer.
The files are (temporarily) available here:
http://people.apache.org/~jgallacher/mod_python/dist/
Please download it, then do the usual
$ ./configure --with-apxs=/wherever/it/is
$ make
$ (su)
# make install
Then (as non-root user!)
$ make check
or if you prefer to run the tests the old way:
$ cd test
$ python test.py
Make a note of any failing tests.
If all the tests pass, give the new module importer a workout by
uncommenting line 328 in test/test.py:
#PythonOption('mod_python.future.importer *'),
and then re-run the tests.
$ make check
And see if any tests fail. If they pass, send a +1 to the list, if they
fail, send the details (the versions of OS, Python and Apache, the test
output, and suggestions, if any).
Thank you for your assistance,
Jim Gallacher
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Nicolas Lehuen <ni...@lehuen.com>.
2006/3/22, Nicolas Lehuen <ni...@lehuen.com>:
> However I have a -1 on Python 2.2 with a LOT of test failures, but I
> guess we won't support Python 2.2 for mod_python 3.3 ?
Sorry, my -1 was due to a configuration problem, everything works on Python 2.2.
+1 for mod_python 3.3.0-dev-20060321 on Windows 2000 SP4 +
ActivePython 2.2.3 + Apache 2.0.55
Regards,
Nicolas
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Nicolas Lehuen <ni...@lehuen.com>.
+1 for mod_python 3.3.0-dev-20060321 on Windows 2000 SP4 +
ActivePython 2.3.5.236 + Apache 2.0.55
However I have a -1 on Python 2.2 with a LOT of test failures, but I
guess we won't support Python 2.2 for mod_python 3.3 ?
Regards,
Nicolas
2006/3/22, Nicolas Lehuen <ni...@lehuen.com>:
> Hi,
>
> Here are the binary for Apache 2.0 :
>
> http://nicolas.lehuen.com/download/mod_python/
>
> I also have a :
>
> +1 for mod_python 3.3.0-dev-20060321 on Windows XP SP2 + ActivePython
> 2.4.2.10 + Apache 2.0.55
>
> Unfortunately I still have some doubts about my tests on Apache
> 2.2.0... I'll see to that this evening.
>
> Regards,
> Nicolas
>
> 2006/3/22, Mike Looijmans <nl...@natlab.research.philips.com>:
> > Nicolas, could you make a Win32 binary for us poor people?
> >
> > --
> > Mike Looijmans
> > Philips Natlab / Topic Automation
> >
> >
>
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Nicolas Lehuen <ni...@lehuen.com>.
Hi,
Here are the binary for Apache 2.0 :
http://nicolas.lehuen.com/download/mod_python/
I also have a :
+1 for mod_python 3.3.0-dev-20060321 on Windows XP SP2 + ActivePython
2.4.2.10 + Apache 2.0.55
Unfortunately I still have some doubts about my tests on Apache
2.2.0... I'll see to that this evening.
Regards,
Nicolas
2006/3/22, Mike Looijmans <nl...@natlab.research.philips.com>:
> Nicolas, could you make a Win32 binary for us poor people?
>
> --
> Mike Looijmans
> Philips Natlab / Topic Automation
>
>
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Mike Looijmans <nl...@natlab.research.philips.com>.
Nicolas, could you make a Win32 binary for us poor people?
--
Mike Looijmans
Philips Natlab / Topic Automation
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Nicolas Lehuen <ni...@lehuen.com>.
I've tested with and without the new importer on Windows XP SP2 +
Python 2.4.2 + Apache 2.2.0 and everything works except the
test_req_auth_type test, which signals a 500 error. This is what the
error_log contains about this test :
[Wed Mar 22 07:16:03 2006] [warn] mod_python
(pid=5140,interpreter='test_req_auth_type'): Module directory listed
in "sys.path". This may cause problems. Please check code. Code file
being imported is "C:\\projets\\mod_python\\test\\htdocs\\tests.py".
[Wed Mar 22 07:16:03 2006] [notice] mod_python
(pid=5140,interpreter='test_req_auth_type'): Importing module
'C:\\projets\\mod_python\\test\\htdocs\\tests.py'
[Wed Mar 22 07:16:03 2006] [crit] [client 127.0.0.1] configuration
error: couldn't check access. No groups file?: /tests.py
[Wed Mar 22 07:16:03 2006] [error] [client 127.0.0.1] No Authn
provider configured
The piece of code that emits the "No groups file?" seem to reside in
libhttpd.dll, a part of Apache 2.2, so I guess it's a problem with my
Apache setup. I'll try this on my Apache 2.0 setup on my PC at work
and let you know.
Regards,
Nicolas
2006/3/22, Jim Gallacher <jp...@jgassociates.ca>:
> mod_python-3.3.0-dev-20060321 is available for testing.
>
> We are asking the mod_python development community for assistance in
> testing the current development branch. Hopefully this will allow us to
> catch new bugs or regressions early, and when we are ready for the next
> release the beta cycle will be much shorter.
>
> This snapshot addresses 33 issues since 3.2.7 was released, including
> apache 2.2 support and the introduction of a new module importer.
>
> The files are (temporarily) available here:
>
> http://people.apache.org/~jgallacher/mod_python/dist/
>
> Please download it, then do the usual
>
> $ ./configure --with-apxs=/wherever/it/is
> $ make
> $ (su)
> # make install
>
> Then (as non-root user!)
>
> $ make check
>
> or if you prefer to run the tests the old way:
>
> $ cd test
> $ python test.py
>
> Make a note of any failing tests.
>
> If all the tests pass, give the new module importer a workout by
> uncommenting line 328 in test/test.py:
>
> #PythonOption('mod_python.future.importer *'),
>
> and then re-run the tests.
>
> $ make check
>
> And see if any tests fail. If they pass, send a +1 to the list, if they
> fail, send the details (the versions of OS, Python and Apache, the test
> output, and suggestions, if any).
>
> Thank you for your assistance,
> Jim Gallacher
>
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Jorey Bump <li...@joreybump.com>.
Jim Gallacher wrote:
> I'm looking for mod_auth_basic.c. Either it's missing or you have it
> compiled as a dynamic module. Could you re-run again using httpd -M? I
> should have asked for that in the first place. :(
~# /usr/local/apache2/bin/httpd -M
Loaded Modules:
core_module (static)
mpm_prefork_module (static)
http_module (static)
so_module (static)
authn_file_module (shared)
authn_dbm_module (shared)
authn_anon_module (shared)
authn_dbd_module (shared)
authn_default_module (shared)
authz_host_module (shared)
authz_groupfile_module (shared)
authz_user_module (shared)
authz_dbm_module (shared)
authz_owner_module (shared)
authz_default_module (shared)
auth_basic_module (shared)
auth_digest_module (shared)
dbd_module (shared)
dumpio_module (shared)
ext_filter_module (shared)
filter_module (shared)
deflate_module (shared)
log_config_module (shared)
log_forensic_module (shared)
logio_module (shared)
env_module (shared)
mime_magic_module (shared)
cern_meta_module (shared)
expires_module (shared)
headers_module (shared)
usertrack_module (shared)
unique_id_module (shared)
setenvif_module (shared)
version_module (shared)
mime_module (shared)
dav_module (shared)
status_module (shared)
autoindex_module (shared)
asis_module (shared)
info_module (shared)
cgi_module (shared)
dav_fs_module (shared)
vhost_alias_module (shared)
negotiation_module (shared)
dir_module (shared)
actions_module (shared)
userdir_module (shared)
alias_module (shared)
rewrite_module (shared)
php5_module (shared)
python_module (shared)
Syntax OK
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Graham Dumpleton <gr...@dscpl.com.au>.
On 23/03/2006, at 5:06 AM, Jim Gallacher wrote:
> That's another reason to rewrite the unit tests. It's too hard to
> sort out the wheat from the chaff.
>
> I don't think this is related to your failing test, but I noticed
> the following, repeated numerous times throughout your log:
>
> [Wed Mar 22 09:09:30 2006] [info] [client 127.0.0.1] (32)Broken
> pipe: core_output_filter: writing data to the network
>
> I think we need to investigate this one.
That is the error I was getting from ab in Apache 2.2. Change test.py to
explicitly use ab from Apache 2.0 and see if they go away.
Graham
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Jim Gallacher <jp...@jgassociates.ca>.
Jorey Bump wrote:
> Jim Gallacher wrote:
>
>> Jorey,
>>
>> This is possibly the same failure Nicolas is seeing on Windows. It
>> could be I've made some incorrect assumptions on the default apache
>> 2.2 configuration such that there is a problem with the test setup.
>>
>> Could you send the output of
>> $ /usr/local/apache2/bin/httpd -l
>
>
> $ /usr/local/apache2/bin/httpd -l
> Compiled in modules:
> core.c
> prefork.c
> http_core.c
> mod_so.c
I'm looking for mod_auth_basic.c. Either it's missing or you have it
compiled as a dynamic module. Could you re-run again using httpd -M? I
should have asked for that in the first place. :(
In the log you sent I see the same error Nicolas mentioned, ie:
[Wed Mar 22 09:05:49 2006] [crit] [client 127.0.0.1] configuration
error: couldn't check access. No groups file?: /tests.py
>> Also dig around in test/logs/error_log and see if you can glean more
>> information on the internal error, or just email me the log off list.
>
>
> It's hard to determine which errors are intentionally caused by the
> tests, so I've sent you the error_log.
That's another reason to rewrite the unit tests. It's too hard to sort
out the wheat from the chaff.
I don't think this is related to your failing test, but I noticed the
following, repeated numerous times throughout your log:
[Wed Mar 22 09:09:30 2006] [info] [client 127.0.0.1] (32)Broken pipe:
core_output_filter: writing data to the network
I think we need to investigate this one.
Jim
>> Jorey Bump wrote:
>>
>>> -1 Slackware 10.1, Apache 2.2.0 (mpm-prefork), Python 2.4
>>>
>>> My applications are working, but make check produces these errors:
>>>
>>> ======================================================================
>>> FAIL: test_req_auth_type (__main__.PerRequestTestCase)
>>> ----------------------------------------------------------------------
>>> Traceback (most recent call last):
>>> File "test.py", line 673, in test_req_auth_type
>>> self.fail(`rsp`)
>>> AssertionError: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML
>>> 2.0//EN">\n<html><head>\n<title>500 Internal Server
>>> Error</title>\n</head><body>\n<h1>Internal Server Error</h1>\n<p>The
>>> server encountered an internal error or\nmisconfiguration and was
>>> unable to complete\nyour request.</p>\n<p>Please contact the server
>>> administrator,\n [no address given] and inform them of the time the
>>> error occurred,\nand anything you might have done that may
>>> have\ncaused the error.</p>\n<p>More information about this error may
>>> be available\nin the server error log.</p>\n</body></html>\n'
>>>
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Jorey Bump <li...@joreybump.com>.
Jim Gallacher wrote:
> Jorey,
>
> This is possibly the same failure Nicolas is seeing on Windows. It could
> be I've made some incorrect assumptions on the default apache 2.2
> configuration such that there is a problem with the test setup.
>
> Could you send the output of
> $ /usr/local/apache2/bin/httpd -l
$ /usr/local/apache2/bin/httpd -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c
> Also dig around in test/logs/error_log and see if you can glean more
> information on the internal error, or just email me the log off list.
It's hard to determine which errors are intentionally caused by the
tests, so I've sent you the error_log.
> Jorey Bump wrote:
>> -1 Slackware 10.1, Apache 2.2.0 (mpm-prefork), Python 2.4
>>
>> My applications are working, but make check produces these errors:
>>
>> ======================================================================
>> FAIL: test_req_auth_type (__main__.PerRequestTestCase)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>> File "test.py", line 673, in test_req_auth_type
>> self.fail(`rsp`)
>> AssertionError: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML
>> 2.0//EN">\n<html><head>\n<title>500 Internal Server
>> Error</title>\n</head><body>\n<h1>Internal Server Error</h1>\n<p>The
>> server encountered an internal error or\nmisconfiguration and was
>> unable to complete\nyour request.</p>\n<p>Please contact the server
>> administrator,\n [no address given] and inform them of the time the
>> error occurred,\nand anything you might have done that may
>> have\ncaused the error.</p>\n<p>More information about this error may
>> be available\nin the server error log.</p>\n</body></html>\n'
>>
>> ----------------------------------------------------------------------
>> Ran 60 tests in 231.452s
>>
>> FAILED (failures=1)
>> F Stopping Apache...
>> /usr/local/apache2/bin/httpd -k stop -f
>> /home/jorey/src/mod_python-3.3.0-dev-20060321/test/conf/test.conf
>>
>> ======================================================================
>> FAIL: testPerRequestTests (__main__.PerInstanceTestCase)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>> File "test.py", line 2467, in testPerRequestTests
>> self.failUnless(result.wasSuccessful())
>> AssertionError
>>
>> ----------------------------------------------------------------------
>>
>> Jim Gallacher wrote:
>>
>>> mod_python-3.3.0-dev-20060321 is available for testing.
>>>
>>> We are asking the mod_python development community for assistance in
>>> testing the current development branch. Hopefully this will allow us
>>> to catch new bugs or regressions early, and when we are ready for the
>>> next release the beta cycle will be much shorter.
>>>
>>> This snapshot addresses 33 issues since 3.2.7 was released, including
>>> apache 2.2 support and the introduction of a new module importer.
>>>
>>> The files are (temporarily) available here:
>>>
>>> http://people.apache.org/~jgallacher/mod_python/dist/
>>>
>>> Please download it, then do the usual
>>>
>>> $ ./configure --with-apxs=/wherever/it/is
>>> $ make
>>> $ (su)
>>> # make install
>>>
>>> Then (as non-root user!)
>>>
>>> $ make check
>>>
>>> or if you prefer to run the tests the old way:
>>>
>>> $ cd test
>>> $ python test.py
>>>
>>> Make a note of any failing tests.
>>>
>>> If all the tests pass, give the new module importer a workout by
>>> uncommenting line 328 in test/test.py:
>>>
>>> #PythonOption('mod_python.future.importer *'),
>>>
>>> and then re-run the tests.
>>>
>>> $ make check
>>>
>>> And see if any tests fail. If they pass, send a +1 to the list, if they
>>> fail, send the details (the versions of OS, Python and Apache, the test
>>> output, and suggestions, if any).
>>>
>>> Thank you for your assistance,
>>> Jim Gallacher
>>
>>
>>
>
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Jim Gallacher <jp...@jgassociates.ca>.
Jorey,
This is possibly the same failure Nicolas is seeing on Windows. It could
be I've made some incorrect assumptions on the default apache 2.2
configuration such that there is a problem with the test setup.
Could you send the output of
$ /usr/local/apache2/bin/httpd -l
Also dig around in test/logs/error_log and see if you can glean more
information on the internal error, or just email me the log off list.
Thanks,
Jim
Jorey Bump wrote:
> -1 Slackware 10.1, Apache 2.2.0 (mpm-prefork), Python 2.4
>
> My applications are working, but make check produces these errors:
>
> ======================================================================
> FAIL: test_req_auth_type (__main__.PerRequestTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "test.py", line 673, in test_req_auth_type
> self.fail(`rsp`)
> AssertionError: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML
> 2.0//EN">\n<html><head>\n<title>500 Internal Server
> Error</title>\n</head><body>\n<h1>Internal Server Error</h1>\n<p>The
> server encountered an internal error or\nmisconfiguration and was unable
> to complete\nyour request.</p>\n<p>Please contact the server
> administrator,\n [no address given] and inform them of the time the
> error occurred,\nand anything you might have done that may have\ncaused
> the error.</p>\n<p>More information about this error may be
> available\nin the server error log.</p>\n</body></html>\n'
>
> ----------------------------------------------------------------------
> Ran 60 tests in 231.452s
>
> FAILED (failures=1)
> F Stopping Apache...
> /usr/local/apache2/bin/httpd -k stop -f
> /home/jorey/src/mod_python-3.3.0-dev-20060321/test/conf/test.conf
>
> ======================================================================
> FAIL: testPerRequestTests (__main__.PerInstanceTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "test.py", line 2467, in testPerRequestTests
> self.failUnless(result.wasSuccessful())
> AssertionError
>
> ----------------------------------------------------------------------
>
> Jim Gallacher wrote:
>
>> mod_python-3.3.0-dev-20060321 is available for testing.
>>
>> We are asking the mod_python development community for assistance in
>> testing the current development branch. Hopefully this will allow us
>> to catch new bugs or regressions early, and when we are ready for the
>> next release the beta cycle will be much shorter.
>>
>> This snapshot addresses 33 issues since 3.2.7 was released, including
>> apache 2.2 support and the introduction of a new module importer.
>>
>> The files are (temporarily) available here:
>>
>> http://people.apache.org/~jgallacher/mod_python/dist/
>>
>> Please download it, then do the usual
>>
>> $ ./configure --with-apxs=/wherever/it/is
>> $ make
>> $ (su)
>> # make install
>>
>> Then (as non-root user!)
>>
>> $ make check
>>
>> or if you prefer to run the tests the old way:
>>
>> $ cd test
>> $ python test.py
>>
>> Make a note of any failing tests.
>>
>> If all the tests pass, give the new module importer a workout by
>> uncommenting line 328 in test/test.py:
>>
>> #PythonOption('mod_python.future.importer *'),
>>
>> and then re-run the tests.
>>
>> $ make check
>>
>> And see if any tests fail. If they pass, send a +1 to the list, if they
>> fail, send the details (the versions of OS, Python and Apache, the test
>> output, and suggestions, if any).
>>
>> Thank you for your assistance,
>> Jim Gallacher
>
>
>
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Jorey Bump <li...@joreybump.com>.
-1 Slackware 10.1, Apache 2.2.0 (mpm-prefork), Python 2.4
My applications are working, but make check produces these errors:
======================================================================
FAIL: test_req_auth_type (__main__.PerRequestTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File "test.py", line 673, in test_req_auth_type
self.fail(`rsp`)
AssertionError: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML
2.0//EN">\n<html><head>\n<title>500 Internal Server
Error</title>\n</head><body>\n<h1>Internal Server Error</h1>\n<p>The
server encountered an internal error or\nmisconfiguration and was unable
to complete\nyour request.</p>\n<p>Please contact the server
administrator,\n [no address given] and inform them of the time the
error occurred,\nand anything you might have done that may have\ncaused
the error.</p>\n<p>More information about this error may be
available\nin the server error log.</p>\n</body></html>\n'
----------------------------------------------------------------------
Ran 60 tests in 231.452s
FAILED (failures=1)
F Stopping Apache...
/usr/local/apache2/bin/httpd -k stop -f
/home/jorey/src/mod_python-3.3.0-dev-20060321/test/conf/test.conf
======================================================================
FAIL: testPerRequestTests (__main__.PerInstanceTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
File "test.py", line 2467, in testPerRequestTests
self.failUnless(result.wasSuccessful())
AssertionError
----------------------------------------------------------------------
Jim Gallacher wrote:
> mod_python-3.3.0-dev-20060321 is available for testing.
>
> We are asking the mod_python development community for assistance in
> testing the current development branch. Hopefully this will allow us to
> catch new bugs or regressions early, and when we are ready for the next
> release the beta cycle will be much shorter.
>
> This snapshot addresses 33 issues since 3.2.7 was released, including
> apache 2.2 support and the introduction of a new module importer.
>
> The files are (temporarily) available here:
>
> http://people.apache.org/~jgallacher/mod_python/dist/
>
> Please download it, then do the usual
>
> $ ./configure --with-apxs=/wherever/it/is
> $ make
> $ (su)
> # make install
>
> Then (as non-root user!)
>
> $ make check
>
> or if you prefer to run the tests the old way:
>
> $ cd test
> $ python test.py
>
> Make a note of any failing tests.
>
> If all the tests pass, give the new module importer a workout by
> uncommenting line 328 in test/test.py:
>
> #PythonOption('mod_python.future.importer *'),
>
> and then re-run the tests.
>
> $ make check
>
> And see if any tests fail. If they pass, send a +1 to the list, if they
> fail, send the details (the versions of OS, Python and Apache, the test
> output, and suggestions, if any).
>
> Thank you for your assistance,
> Jim Gallacher
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Jim Gallacher <jp...@jgassociates.ca>.
+1 Linux Debian Sid, apache 2.0.55 mpm-prefork, python 2.3.5
+1 Linux Debian Sid, apache 2.2.0 mpm-prefork, python 2.4.2
New Importer:
+1 Linux Debian Sid, apache 2.0.55 mpm-prefork, python 2.3.5
+1 Linux Debian Sid, apache 2.2.0 mpm-prefork, python 2.4.2
Jim Gallacher wrote:
> mod_python-3.3.0-dev-20060321 is available for testing.
>
> We are asking the mod_python development community for assistance in
> testing the current development branch. Hopefully this will allow us to
> catch new bugs or regressions early, and when we are ready for the next
> release the beta cycle will be much shorter.
>
> This snapshot addresses 33 issues since 3.2.7 was released, including
> apache 2.2 support and the introduction of a new module importer.
>
> The files are (temporarily) available here:
>
> http://people.apache.org/~jgallacher/mod_python/dist/
>
> Please download it, then do the usual
>
> $ ./configure --with-apxs=/wherever/it/is
> $ make
> $ (su)
> # make install
>
> Then (as non-root user!)
>
> $ make check
>
> or if you prefer to run the tests the old way:
>
> $ cd test
> $ python test.py
>
> Make a note of any failing tests.
>
> If all the tests pass, give the new module importer a workout by
> uncommenting line 328 in test/test.py:
>
> #PythonOption('mod_python.future.importer *'),
>
> and then re-run the tests.
>
> $ make check
>
> And see if any tests fail. If they pass, send a +1 to the list, if they
> fail, send the details (the versions of OS, Python and Apache, the test
> output, and suggestions, if any).
>
> Thank you for your assistance,
> Jim Gallacher
>
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Mike Looijmans <nl...@natlab.research.philips.com>.
Jim Gallacher wrote:
> Mike Looijmans wrote:
>> And in addition to running the unit tests, try running your actual web
>> site with this release. That usually manages to bring up things the
>> developers never thought of - so that we can extend the unit tests
>> with those cases as well. I can imagine that some code may depend on
>> some specific behaviour of FieldStorage for example.
>
> As nice as it would be to get some real-world feedback, let's not forget
> this is a *development* snapshot, and should not be considered stable
> for production use. Test your application on your website development
> machine if you can - the more testing the better. I'm sure that is what
> Mike meant, but I just want to make it clear that we are not suggesting
> this is a release candidate for production use.
From my post that intention wasn't clear, so thanks Jim for pointing
that out. Want I wanted to write is to run your site's code on it, but
not (necessarily) your production site. Most of us will have some
development system where they check things out and/or do development and
testing before putting them into the field.
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Jim Gallacher <jp...@jgassociates.ca>.
Mike Looijmans wrote:
> And in addition to running the unit tests, try running your actual web
> site with this release. That usually manages to bring up things the
> developers never thought of - so that we can extend the unit tests with
> those cases as well. I can imagine that some code may depend on some
> specific behaviour of FieldStorage for example.
As nice as it would be to get some real-world feedback, let's not forget
this is a *development* snapshot, and should not be considered stable
for production use. Test your application on your website development
machine if you can - the more testing the better. I'm sure that is what
Mike meant, but I just want to make it clear that we are not suggesting
this is a release candidate for production use.
Jim
Re: mod_python 3.3.0-dev-20060321 available for testing
Posted by Mike Looijmans <nl...@natlab.research.philips.com>.
And in addition to running the unit tests, try running your actual web
site with this release. That usually manages to bring up things the
developers never thought of - so that we can extend the unit tests with
those cases as well. I can imagine that some code may depend on some
specific behaviour of FieldStorage for example.
--
Mike Looijmans
Philips Natlab / Topic Automation
Jim Gallacher wrote:
> mod_python-3.3.0-dev-20060321 is available for testing.
>
> We are asking the mod_python development community for assistance in
> testing the current development branch. Hopefully this will allow us to
> catch new bugs or regressions early, and when we are ready for the next
> release the beta cycle will be much shorter.
>
> This snapshot addresses 33 issues since 3.2.7 was released, including
> apache 2.2 support and the introduction of a new module importer.
>
> The files are (temporarily) available here:
>
> http://people.apache.org/~jgallacher/mod_python/dist/
>
> Please download it, then do the usual
>
> $ ./configure --with-apxs=/wherever/it/is
> $ make
> $ (su)
> # make install
>
> Then (as non-root user!)
>
> $ make check
>
> or if you prefer to run the tests the old way:
>
> $ cd test
> $ python test.py
>
> Make a note of any failing tests.
>
> If all the tests pass, give the new module importer a workout by
> uncommenting line 328 in test/test.py:
>
> #PythonOption('mod_python.future.importer *'),
>
> and then re-run the tests.
>
> $ make check
>
> And see if any tests fail. If they pass, send a +1 to the list, if they
> fail, send the details (the versions of OS, Python and Apache, the test
> output, and suggestions, if any).
>
> Thank you for your assistance,
> Jim Gallacher
>