./www/py-mod_wsgi, WSGI module for apache

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 4.7.1, Package name: py37-ap24-mod_wsgi-4.7.1, Maintainer: pkgsrc-users

The aim of mod_wsgi is to implement a simple to use Apache module which can
host any Python application which supports the Python WSGI interface.
The module would be suitable for use in hosting high performance production web
sites, as well as your average personal sites running on commodity web hosting
services.


Required to run:
[devel/py-setuptools] [www/apache24] [lang/python37]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 155b0e2931f875c6294db4a6f7a82c7f34e0b2c9
RMD160: 4c920f6723f73cb09d7ea239ede5d3a0e55e656c
Filesize: 486.622 KB

Version history: (Expand)


CVS history: (Expand)


   2020-06-20 18:36:49 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-mod_wsgi: updated to 4.7.1

Version 4.7.1

Bugs Fixed

Fix up installation on Windows into a virtual environment when using latest \ 
virtualenv version, or recent Python versions with the bundled venv module for \ 
creating virtual environments.

Version 4.7.0

New Features

Now releasing parallel mod_wsgi-standalone package to PyPi. This is the same as \ 
the mod_wsgi package, except that by installing the mod_wsgi-standalone package, \ 
it will automatically trigger the mod_wsgi-httpd package to install the Apache \ 
HTTPD server as part of your Python installation. When you run mod_wsgi-express \ 
it will use that Apache HTTPD server installation.

The mod_wsgi-standalone package is required where you need to install \ 
mod_wsgi-express using its own Apache HTTPD installation due to no system Apache \ 
HTTPD server package being available, and the installation needs to be done \ 
using a requirements.txt file for pip or other package install manager. Using \ 
mod_wsgi-standalone will ensure that the mod_wsgi-httpd package is installed \ 
first before attempting to build and install mod_wsgi. This guarantee is not \ 
provided by pip if you list mod_wsgi-httpd and mod_wsgi packages as two entries.

The version numbering of the mod_wsgi-standalone package will follow the \ 
mod_wsgi versioning.
   2020-05-13 06:43:01 by Roland Illig | Files touched by this commit (2)
Log message:
www/py-mod_wsgi: fix bashism in configure script
   2019-07-03 21:50:33 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-mod_wsgi: updated to 4.6.7

Version 4.6.7:

Bugs Fixed
Fix Windows build errors due to Python 3.7+ not providing empty function stubs \ 
for PyOS_AfterFork_Child() and PyOS_AfterFork_Parent().

Version 4.6.6:

Bugs Fixed
Fix compilation failures when using Python 3.8.

Features Changed
When running mod_wsgi-express it will do a search for the location of bash and \ 
sh when defining the shell to use for the generated apachectl. The shell used \ 
can be overridden using --shell-executable option. This is to get around issue \ 
with FreeBSD not having /bin/bash.

New Features
The Apache request ID is accessible in request events as request_id.
The per request data dictionary accessible using mod_wsgi.request_data() is now \ 
also accessible in events as request_data.
   2018-12-11 10:46:23 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
py-mod_wsgi: updated to 4.6.5

Version 4.6.5

Bugs Fixed
* When running mod_wsgi-express and serving up static files from the document \ 
root, and the WSGI application was mounted at a sub URL using --mount-point, the \ 
static files in the document root outside of the mount point for the WSGI \ 
application would no longer be accessible.
* If no system mime types file can be found, fall back to /dev/null so that \ 
Apache can still at least start up.

Features Changed
* On macOS, use /var/tmp as default parent directory for server root directory \ 
rather than value of $TMPDIR. The latter can produce a path which is too long \ 
and UNIX socket cannot be written there.

New Features
* Now possible to use mod_wsgi-express in an a zipapp created using shiv. This \ 
entailed a special workaround to detect when shiv was used, so that the unpacked \ 
site-packages directory could be added to the Python module search path for \ 
mod_wsgi-express.
   2018-04-14 11:34:15 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-mod_wsgi: updated to 4.6.4

Version 4.6.4:
Bugs Fixed
In more recent Python versions, the config directory in the Python installation \ 
incorporates the platform name. This directory was added as an additional \ 
directory to search for Python shared libraries when installing using the \ 
setup.py file or pip. It should not even be needed for newer Python versions but \ 
still check for older Python versions. The only issue arising from the wrong \ 
directory, not incorporating the platform name, being used, was a linker warning \ 
about the directory not being present.

Installing mod_wsgi on Windows would fail as hadn’t exclude mod_wsgi daemon \ 
mode specific code from Windows build. This would result in compile time error \ 
about wsgi_daemon_process being undefined. This problem was introduced to \ 
Windows in version 4.6.0. A prior attempt to fix this in 4.6.3 missed one place \ 
in the code which needed to be changed.

Version 4.6.3
Bugs Fixed

When compiled for Python 2.6, when run mod_wsgi would fail to load into Apache \ 
due to misisng symbol PyFrame_GetLineNumber. This was only introduced in Python \ 
2.7. Use alternate way to get line number which still yields correct answer. \ 
This issue was introduced in mod_wsgi version 4.6.0 in fix to have correct line \ 
numbers generated for stack traces on shutdown due to request timeout.

Installing mod_wsgi on Windows would fail as hadn’t exclude mod_wsgi daemon \ 
mode specific code from Windows build. This would result in compile time error \ 
about wsgi_daemon_process being undefined. This problem was introduced to \ 
Windows in version 4.6.0.

When using runmodwsgi management command integration for Django, the file \ 
containing the WSGI application entry point was specified via a full filesystem \ 
path, rather than by module import path. This meant that relative imports from \ 
that file would fail. The file is now imported as a module path based on what \ 
WSGI_APPLICATION is set to in the Django settings module. This means the file is \ 
imported as part of package for the project and relative imports will work.
   2018-01-01 11:23:09 by Thomas Klausner | Files touched by this commit (145)
Log message:
apache22: remove, it was eol'd in June 2017

Remove packages that only work with apache22.
Remove apache22 references.
   2017-12-17 16:38:23 by Adam Ciarcinski | Files touched by this commit (1) | Package updated
Log message:
PLIST should have also been updated
   2017-12-16 08:46:30 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-mod_wsgi: updated to 4.5.24

Version 4.5.24:
Bugs Fixed
Using mod_wsgi in daemon mode on Solaris would cause a process hang or max out \ 
CPU usage. Caused by change of variable type to unsigned to get rid of compiler \ 
warnings, without fixing how condition check using variable was done.

Problem could also affect non Solaris systems if total number of HTTP headers \ 
and other variables passed in WSGI environ was greater than 1024. Affected \ 
Solaris all the time due to it having a limit of only 16 in operating system for \ 
same code, meaning hit problem immediately.