Skip to content

Commit 14b71d2

Browse files
Merge branch 'release/4.1.1'
2 parents 6af0947 + 5729262 commit 14b71d2

File tree

5 files changed

+43
-2
lines changed

5 files changed

+43
-2
lines changed

docs/release-notes/index.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ Release Notes
55
.. toctree::
66
:maxdepth: 2
77

8+
version-4.1.1.rst
89
version-4.1.0.rst
910

1011
version-4.0.rst

docs/release-notes/version-4.1.0.rst

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ initialised to signal that it should be shutdown, the process could crash
3434
rather than shutdown properly due to not registering the signal pipe
3535
prior to registering signal handler.
3636

37-
2. Python doesn't initialise codes in sub interpreters automatically which
37+
2. Python doesn't initialise codecs in sub interpreters automatically which
3838
in some cases could cause code running in WSGI script to fail due to lack
3939
of encoding for Unicode strings when converting them. The error message
4040
in this case was::
@@ -122,6 +122,21 @@ long running request. See the new ``request-timeout`` option for a way of
122122
interrupting long running, potentially blocked requests and restarting
123123
the process.
124124

125+
5. If the ``home`` option is used with ``WSGIDaemonProcess``, in addition
126+
to that directory being made the current working directory for the process,
127+
an empty string will be added to the start of the Python module search
128+
path. This causes Python to look in the current working directory for
129+
Python modules when they are being imported.
130+
131+
This behaviour brings things into line with what happens when running the
132+
Python interpreter from the command line. You must though be using the
133+
``home`` option for this to come into play.
134+
135+
Do not that if your application then changes the working directory, it
136+
will start looking in the new current working directory and not that which
137+
is specified by the ``home`` option. This again mirrors what the normal
138+
Python command line interpreter does.
139+
125140
New Features
126141
------------
127142

docs/release-notes/version-4.1.1.rst

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
=============
2+
Version 4.1.1
3+
=============
4+
5+
Version 4.1.1 of mod_wsgi can be obtained from:
6+
7+
https://github.com/GrahamDumpleton/mod_wsgi/archive/4.1.1.tar.gz
8+
9+
Known Issues
10+
------------
11+
12+
1. The makefiles for building mod_wsgi on Windows are currently broken and
13+
need updating. As most new changes relate to mod_wsgi daemon mode, which is
14+
not supported under Windows, you should keep using the last available
15+
binary for version 3.X on Windows instead.
16+
17+
Bugs Fixed
18+
----------
19+
20+
1. Compilation would fail on Apache 2.4 due to a change in the Apache API to
21+
determine the name of the MPM being used.

src/server/wsgi_apache.h

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -98,6 +98,10 @@ APLOG_USE_MODULE(wsgi);
9898
#define APR_FPROT_WWRITE APR_WWRITE
9999
#endif
100100

101+
#ifndef MPM_NAME
102+
#define MPM_NAME ap_show_mpm()
103+
#endif
104+
101105
#if !AP_MODULE_MAGIC_AT_LEAST(20050127,0)
102106
/* Debian backported ap_regex_t to Apache 2.0 and
103107
* thus made official version checking break. */

src/server/wsgi_version.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
#define MOD_WSGI_MAJORVERSION_NUMBER 4
2727
#define MOD_WSGI_MINORVERSION_NUMBER 1
2828
#define MOD_WSGI_MICROVERSION_NUMBER 0
29-
#define MOD_WSGI_VERSION_STRING "4.1.0"
29+
#define MOD_WSGI_VERSION_STRING "4.1.1"
3030

3131
/* ------------------------------------------------------------------------- */
3232

0 commit comments

Comments
 (0)