bash 3.1.x gets shell quoting wrong, causing configure to fail on platforms
that use this shell
New in this version according to
http://www.modpython.org/live/mod_python-3.2.10/doc-html/node98.html:
- Added support for Apache 2.2.
- New req.is_https() and req.ssl_var_lookup() methods. These communicate
direct with the Apache mod_ssl module, allowing it to be determined if
the connection is using SSL/TLS and what the values of internal ssl
variables are.
- New req.server.get_options() method. This returns the subset of Python
options set at global scope within the Apache configuration. That is,
outside of the context of any VirtualHost, Location, Directory or Files
directives.
- The directory used for mutex locks can now be specified at at compile
time using ./configure --with-mutex-dir value or at run time with
PythonOption mod_python.mutex_directory value.
- The number of mutex locks can now be specified at run time with
PythonOption mod_python.mutex_locks value.
- Fixed three memory leaks that were found in _apachemodule.parse_qsl,
req.readlines and util.cfgtree_walk.
- Third party C modules that use the simplified API for the Global Interpreter
Lock (GIL), as described in PEP 311, can now be used. The only requirement
is that such modules can only be used in the context of the "main_interpreter".
- DbmSession unit test no longer uses the default directory for the dbm file,
so the test will not interfer with the user's current apache instance.
- Added additional debugging and logging output for where mod_python cannot
initialise itself properly due to Python or mod_python version mismatches or
missing Python module code files.
- Fixed configure problem when using bash 3.1.x.
- Fixed DbmSession to create db file with mode 0640.
- Fixed request.sendfile() bug for symlinked files on Win32.
bb75615363