-
Notifications
You must be signed in to change notification settings - Fork 270
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
6 changed files
with
48 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
============= | ||
Version 4.6.3 | ||
============= | ||
|
||
Version 4.6.3 of mod_wsgi can be obtained from: | ||
|
||
https://codeload.github.com/GrahamDumpleton/mod_wsgi/tar.gz/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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters