diff options
| author | Graham Dumpleton <Graham.Dumpleton@gmail.com> | 2018-03-26 10:49:57 +1100 |
|---|---|---|
| committer | Graham Dumpleton <Graham.Dumpleton@gmail.com> | 2018-03-26 10:49:57 +1100 |
| commit | 126e60a6c83d8645fd512d97df7047454a0742c1 (patch) | |
| tree | 850ec9da12ecdb76e6b2446626a2b6e55f4d6356 /docs/release-notes | |
| parent | 5afe5abf8e47f2b7a712847e4ef936e63accb513 (diff) | |
| download | mod_wsgi-126e60a6c83d8645fd512d97df7047454a0742c1.tar.gz | |
Import Django WSGI application as module not script file path so relative imports work.
Diffstat (limited to 'docs/release-notes')
| -rw-r--r-- | docs/release-notes/version-4.6.3.rst | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/release-notes/version-4.6.3.rst b/docs/release-notes/version-4.6.3.rst index f787629..d06dc83 100644 --- a/docs/release-notes/version-4.6.3.rst +++ b/docs/release-notes/version-4.6.3.rst @@ -20,3 +20,11 @@ Bugs Fixed 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. |