/
CHANGES.txt
266 lines (167 loc) · 7.26 KB
/
CHANGES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
=======
CHANGES
=======
4.0.0a4 (unreleased)
--------------------
- Improve Trove classifiers.
4.0.0a3 (2013-03-03)
--------------------
- You can now specify additional WSGI middleware components wihtout
subclassing the ``BrowserLayer`` class.
- `tox` now uses the Zope test runner's `ftest` command to execute tests,
since setup tests cannot deal with layers, especially when they need to
spawn sub-proceeses.
- Switched all functional tests to use `WebTest` instead of
``zope.testbrowser``. Setup proper layering.
- Do not rely on ``zope.testbrowser.wsgi`` WSGI layer support. It was not
needed anyways.
- Minimized the ``ftesting.zcml`` setup.
4.0.0a2 (2013-03-02)
--------------------
- Fixed a bug in WSGI Test Layer setup, where the DB is not correctly set.
4.0.0a1 (2013-02-28)
--------------------
- Added support for Python 3.3.
- Replaced deprecated ``zope.interface.implements`` usage with equivalent
``zope.interface.implementer`` decorator.
- Dropped support for Python 2.4 and 2.5.
3.15.0 (2012-01-19)
-------------------
- Fixed: zope.app.wsgi.paste.ZopeApplication didn't emit
ProcessStarting events.
**NOTE**
If an application compensated for this by generating the event, it
will need to stop or there will be multiple events
emited. (Whether or not multiple events will do any harm is
application specific.)
3.14.0 (2012-01-10)
-------------------
- Set the WSGI environment's ``REMOTE_USER`` item (if not already set)
with the Zope principal label. (This is the same data set in
the ``wsgi.logging_info`` environment item.)
This change allows user info to be used by `paste.translogger
<http://pythonpaste.org/modules/translogger.html>`_ middleware (or
any similar middleware that uses ``REMOTE_USER``), which provides
access logging.
3.13.0 (2011-03-15)
-------------------
- Update to zope.testbrowser 4.0.0 which uses WebTest instead of wsgi_intercept.
3.12.0 (2011-01-25)
-------------------
- Fixed ``zope.app.wsgi.testlayer.http`` to work with changes made in
version 3.11.0.
3.11.0 (2011-01-24)
-------------------
- Moved `wsgi_intercept` support to ``zope.testbrowser.wsgi``, thus
requiring at least version 3.11 of this package:
- Moved ``zope.app.wsgi.testlayer.Browser`` to
``zope.testbrowser.wsgi.Browser``, but left BBB import here.
- Split up ``zope.app.wsgi.testlayer.BrowserLayer`` into generic WSGI
browser layer (``zope.testbrowser.wsgi.Layer``) and ZODB/ZOPE specific
part (``zope.app.wsgi.testlayer.BrowserLayer`` as before).
3.10.0 (2010-11-18)
-------------------
- Add pluggability for setting up WSGI middleware in testlayer.
3.9.3 (2010-10-14)
------------------
- Python 2.7 compatibility for xmlrpc. Transplant of zope.app.testing r116141.
3.9.2 (2010-05-23)
------------------
- Fixed test breakage due to changes in mechanize 0.2.0.
3.9.1 (2010-04-24)
------------------
- Add support for testing XMLRPC using zope.app.wsgi.testlayer.
- Fix a bug in the status string handling in zope.app.wsgi.testlayer's
FakeResponse.
3.9.0 (2010-04-19)
------------------
- Return a FakeResponse object in zope.app.wsgi.testlayer.http,
so it becomes easier to port over tests from zope.app.testing's
HTTPCaller.
- X-Powered-By header is now stripped by zope.app.wsgi.testlayer as
it is by zope.app.testing.
- Bugfix: initialize any <logger> defined in the config, as
zope.app.server does. (Fixes #291147)
3.8.0 (2010-04-14)
------------------
- zope.app.wsgi.testlayer is now a lot more compatible with
the HTTPCaller() functionality in zope.app.testing, which it can
replace:
- same transaction behavior - pending transactions are committed
before request and synchronized afterwards.
- support for browser.handleErrors (for zope.testbrowser).
- support for clear-text (non-base64) Basic authentication headers,
which are easier to read in the tests (though not correct in
actual HTTP traffic).
3.7.0 (2010-04-13)
------------------
- Rewrite tests in order not to dependent on ``zope.app.testing`` and
``zope.app.zcmlfiles``.
- ``zope.app.wsgi.testlayer`` introduces new testing functionality that
can replace the old functionality in ``zope.app.testing``. In addition,
it supports using ``zope.testbrowser`` with WSGI directly (instead of
relying on ``zope.app.testing``, which pulls in a lot of dependencies).
The interesting parts are:
* ``zope.app.wsgi.testlayer.BrowserLayer``: this sets up a minimal layer
that allows you to use the new WSGI-enabled Browser.
* ``zope.app.wsgi.testlayer.Browser``: this is a subclass of Browser from
``zope.testbrowser.browser``. Use it instead of
``zope.testbrowser.browser`` directly to use the test browser with WSGI.
You need to use ``BrowserLayer`` with your tests for this to work.
* ``zope.app.wsgi.testlayer.http``: this is the equivalent to the ``http()``
function in ``zope.app.testing``. It allows low-level HTTP access
through WSGI. You need to use ``BrowserLayer`` with your tests for
this to work.
3.6.1 (2010-01-29)
------------------
- Support product configuration sections in Zope configuration files.
3.6.0 (2009-06-20)
------------------
- Import database events directly from ``zope.processlifetime``
instead of using BBB imports in ``zope.app.appsetup``.
3.5.2 (2009-04-03)
------------------
- The ``WSGIPublisherApplication`` uses now the ``ILoggingInfo`` concept given
from zope.publisher.interfaces.logginginfo for log user infos usable for
access logs. This allows you to implement your own access log user info
message. See zope.publisher.interfaces.logginginfo.ILoggingInfo for more
information.
3.5.1 (2009-03-31)
------------------
- The ``WSGIPublisherApplication`` call now provides a user name
in the environment meant for use in logs.
3.5.0 (2009-02-10)
------------------
- Make devmode warning message more generic. We don't nesessary have the
`etc/zope.conf` file nowadays when using buildout-based setups.
- Add an application factory for Paste. So Zope application can now be
easily deployed with Paste .ini configuration like this::
[app:main]
use = egg:zope.app.wsgi
config_file = %(here)s/zope.conf
handle_errors = false
The config_file is a required argument, however the handle_errors
defaults to True if not specified. Setting it to False allows you to
make WSGIPublisherApplication not handle exceptions itself but
propagate them to an upper middleware, like WebError or something.
- The ``WSGIPublisherApplication`` constructor and ``getWSGIApplication``
function now accept optional ``handle_errors`` argument, described
above.
- Change mailing list address to zope-dev at zope.org instead of retired
one.
3.4.1 (2008-07-30)
------------------
- Added Trove classifiers.
- Notify ``WSGIPublisherApplicationCreated`` event when WSGI application is
created.
- Fixed deprecation warning in ``ftesting.zcml``: ZopeSecurityPolicy moved to
``zope.securitypolicy``.
3.4.0 (2007-09-14)
------------------
- Fixed the tests to run on Python 2.5 as well as Python 2.4.
- Split ``getApplication`` into ``config`` and ``getApplication`` so
that ``config`` could be reused, for example for debugging.
3.4.0a1 (2007-04-22)
--------------------
Initial release as a separate project, corresponds to ``zope.app.wsgi``
from Zope 3.4.0a1