list that was being modified as we went).
[Backport from Zope3; I'm not actually sure if the list returned by
**Btree.keys() is lazy, but I assume it is.]

        # DB 4.1.24 requires that operations happening in a transaction must
        # be performed on a database that was opened in a transaction.  Since
        # we do the former, we must do the latter.  However, earlier DB
        # versions don't transactionally protect database open, so this is the
        # most portable way to write the code.

i.e. we use the DB_AUTO_COMMIT flag for the open, if it's defined.

right thing to do anyway, and should work just find for earlier
versions of the wrapper.  Specifically,

_dorecovery(), _collect_objs(), _mark(): transactionally protect
.truncate() and .consume()

_docommit(): Move the setting of the _pending flag to here from
_finish() so we can transactionally protect it more conveniently.
This does't change the semantics and the recovery code in _setupDBs()
doesn't care since the flag will already be set to COMMIT.

right thing to do anyway, and should work just find for earlier
versions of the wrapper.  Specifically,

_doabort(), _docommit(), _mark(), _sweep(), _collect_objs():
Transactionally protect .truncate() and .consume()

_docommit(): Move the setting of the _pending flag to here from
_finish() so we can transactionally protect it more conveniently.
This does't change the semantics and the recovery code in _setupDBs()
doesn't care since the flag will already be set to COMMIT.

_begin(): Transactionally protect the setting of the _pending flag to
ABORT.

I couldn't find any references to cPickle in any of the setup/build
tools, but I couldn't actually verify that the Windows build was
unaffected.

Added ZPL header to stopper test module

Python 2.2.X version

- logging an error message instead of raising an exception in case of
  unindex_object() failure

      - Collector #699: MailHosts created in 2.5 breaks in 2.6.

      - Collector #694: dtml-sendmail mailto specification replaces "To:" header.

Normalize whitespace (horizontal and vertical).

confusion caused by having the instance and the class have the same
name.

ChrisM's changes here) it is no longer necessary to call
zLOG.initialize() in order to see logging output.

least 2.2.2.)

Add -v1 to TESTOPTS, so running the entire test suite is a little less
verbose.

Stringify the object in the exception in case its a list or tuple (an inscrutable error occurs if this is not done).

_doclose() twice (runsvr.py had a bug that caused the storages to be
closed twice).

Allowing DA to have an option connection hook which allows you to change the database connection at run time for a sqlmethod.

close(): The base class can now do all the work of closing, including
stopping the background threads.

log(): Much more convenient.

do the build in *this* version of Zope.

  severity level.  This allows the common names to be used for
  severities, not just integers.  This can make configuration data
  less obscure.

- Refactor initialize():
  get_environment_info() pulls information from the environment
  variables, and this gets passed to initialize_log(), which does
  nothing to determine the source of the configuration data.

- New method initialize_with_config():  Load information not provided
  by the environment from a ZConfig section.  This allows the
  environment to override a config file, and avoids having the
  application deal with the specific information needed to configure
  logging.

Jim suggests that autopack never do a full gc'ing pack by default, so
let's set the classicpack default to zero.

__init__(): Pass the absolute path to the DB environment's db_home  as
the name argument to the base class constructor.  This gives a unique
value for sortKeys().

env_from_string(): Keith Bostic suggests we stick with DB_RECOVER.

applied to ttheir modules.

When trusted code or module refreshes ask for a ModuleSecurityInfo object
that was already applied, previously a new one would be created, including
new ones for the parent packages. This could cause declartion for *other*
packages to be removed when this new Info object is reapplied later on.

Change one final use of the old regex module to ts_regex.

know whether this file *should* be used anymore, though.  But if it isn't,
I would have expected "someone" to have removed it by now.