Allow apache22 in some more case and add a hack to devel/subversion
to determine the module by the state of the apache22 option.
This comes from www/ap2-subversion and should be fixed to properly
use build options or so.
OK agc@
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.
Mainly this is to fix a security vulnerability. Other changes:
Mod_python 3.0 no longer works with Apache 1.3, only Apache 2.x is supported.
Mod_python no longer works with Python versions less than 2.2.1
Mod_python now supports Apache filters.
Mod_python now supports Apache connection handlers.
Request object supports internal_redirect().
Connection object has read(), readline() and write().
Server object has get_config().
Httpdapi handler has been deprecated.
Zpublisher handler has been deprecated.
Username is now in req.user instead of req.connection.user
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
Version 3.1.3
Apache module that embeds the Python interpreter
As discussed on the mailing list, this package builds and runs for the
most part but fails if the web server has too many backends. Adding it
breaks nothing and does add functionality. I will file a PR to keep
track of the remaining issue.
