Path to this page:
Subject: CVS commit: pkgsrc/www/py-mod_wsgi
From: Adam Ciarcinski
Date: 2018-04-14 11:34:15
Message id: 20180414093415.C48F0FBEC@cvs.NetBSD.org
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.
Files: