242
- A ZEO threading bug could cause transactions to read inconsistent
243
data. (This sometimes caused an AssertionError in
244
Connection._setstate_noncurrent.)
246
- DemoStorage.loadBefore sometimes returned invalid data which
247
would trigger AssertionErrors in ZODB.Connection.
249
- History support was broken when using stprages that work with ZODB
252
- zope.testing was an unnecessary non-testing dependency.
254
- Internal ZEO errors were logged at the INFO level, rather
255
than at the error level.
257
- The FileStorage backup and restore script, repozo, gave a
258
deprecation warning under Python 2.6.
260
- C Header files weren't installed correctly.
268
- 2 BTree bugs, introduced by a bug fix in 3.9.0c2, sometimes caused
269
deletion of keys to be improperly handled, resulting in data being
270
available via iteraation but not item access.
278
- ZEO manages a separate thread for client network IO. It created
279
this thread on import, which caused problems for applications that
280
implemented daemon behavior by forking. Now, the client thread
281
isn't created until needed.
283
- File-storage pack clean-up tasks that can take a long time
284
unnecessarily blocked other activity.
286
- In certain rare situations, ZEO client connections would hand during
287
the initial connection setup.
236
289
3.9.1 (2009-10-01)
237
290
==================
242
- Conflict errors committing blobs caused servers to stop committing
295
- Conflict errors committing blobs caused ZEO servers to stop committing
245
298
3.9.0 (2009-09-08)
added
removed
PKG-INFO
