|
Home > Archive > Apache Mod-Python > November 2006 > mod_python 3.3.0-dev-20061109 available for testing (release candidate)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
mod_python 3.3.0-dev-20061109 available for testing (release candidate)
|
|
| Jim Gallacher 2006-11-13, 8:13 am |
| The mod_python 3.3-0-dev-20061109 tarball is available for testing.
We are almost ready for a 3.3.0 release. It's been a while since we've
had extensive testing of trunk and I think it would be wise to have a
preliminary testing round. Unless there are huge problems we'll do an
official beta next week. If it looks *really* good we might even jump
right to the release.
At this point svn trunk should be considered frozen execpt to fix issues
that testing exposes or minor documentation changes.
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
should feel obligated to :-) ) test it, and provide feedback *to _this_
list*! (Not the mod_python@modpython.org list, and preferably not me
personally).
The files are (temporarily) available here:
http://people.apache.org/~jgallacher/mod_python/dist/
http://people.apache.org/~jgallache...ev-20061109.tgz
http://people.apache.org/~jgallache...0061109.tgz.md5
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 for you Windows folks
$ cd test
$ Python test.py
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, Apache, Apache-mpm, Python,
the test output, and suggestions, if any).
Please present your test results in the following format:
+1 OS version, Apache version (apache mpm), Python Version
For example:
+1 Linux Debian Sid, Apache 2.0.55 (mpm-worker), Python 2.3.5
Presenting your information in a consistent format will help in
tabulating the results. You can include additional information in each
section, just don't use extra commas. There is no need to include the
mod_python version in this string as that information is available in
the email subject. Who knows, one day I may actually write a script to
extract this information automatically. 
Thank you for your assistance,
Jim Gallacher
| |
| Graham Dumpleton 2006-11-13, 8:13 am |
| I'm biased, but:
+1 Mac OS X 10.4.7, Apache 2.0.59 (mpm-worker), Python 2.3.5
+1 Mac OS X 10.4.7, Apache 2.2.2 (mpm-worker), Python 2.3.5
This was with both new importer and old importer.
Ie., for old importer, in test.py uncomment:
PythonOption('mod_python.legacy.importer *'),
I'll try and run the tests on an OpenVPS system this weekend if I get a chance.
I have remembered another issue in code that I think needs to be addressed. I
have been meaning to raise this on a number of times over the last few months,
but for one reason or another have never done so. I'll send a separate email
about this though. It doesn't have to be something that is addressed for this
release, but still should start a discussion on it now before I forget again
and can at least create a JIRA issue about it with any details of what results
from that.
BTW, in case no one noticed, on the 'Installation' page in the new documentation
for this release I have added:
Also check out Graham Dumpleton's assorted articles on mod_python at
http://www.dscpl.com.au/wiki/ModPython/Articles. These include alternate
instructions for getting a first mod_python handler working, as well as articles
covering problems, short comings and constraints in various versions of
mod_python.
If anyone objects to me having added a link off to my personal site where
I keep my own articles on mod_python, please let me know and I can remove
it.
Graham
Jim Gallacher wrote ..
> The mod_python 3.3-0-dev-20061109 tarball is available for testing.
>
> We are almost ready for a 3.3.0 release. It's been a while since we've
> had extensive testing of trunk and I think it would be wise to have a
> preliminary testing round. Unless there are huge problems we'll do an
> official beta next week. If it looks *really* good we might even jump
> right to the release.
>
> At this point svn trunk should be considered frozen execpt to fix issues
> that testing exposes or minor documentation changes.
>
> 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
> should feel obligated to :-) ) test it, and provide feedback *to _this_
> list*! (Not the mod_python@modpython.org list, and preferably not me
> personally).
>
> The files are (temporarily) available here:
>
> http://people.apache.org/~jgallacher/mod_python/dist/
> http://people.apache.org/~jgallache...ev-20061109.tgz
> http://people.apache.org/~jgallache...0061109.tgz.md5
>
> 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 for you Windows folks
>
> $ cd test
> $ Python test.py
>
> 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, Apache, Apache-mpm, Python,
> the test output, and suggestions, if any).
>
> Please present your test results in the following format:
> +1 OS version, Apache version (apache mpm), Python Version
>
> For example:
> +1 Linux Debian Sid, Apache 2.0.55 (mpm-worker), Python 2.3.5
>
> Presenting your information in a consistent format will help in
> tabulating the results. You can include additional information in each
> section, just don't use extra commas. There is no need to include the
> mod_python version in this string as that information is available in
> the email subject. Who knows, one day I may actually write a script to
> extract this information automatically.
>
> Thank you for your assistance,
> Jim Gallacher
|
|
|
|
|