Remove 'python2.2' and 'python2.1' as acceptable executable names, as we're only interested in working under 2.3 now.

Python 2.2.3 and older are no longer acceptable versions of Python to use to run Zope 2.7+, as the logging package was removed from Zope proper and Zope requires it to start up.  The logging package exists in Python 2.3 and better.

Script (Python) objects now have a _filepath attribute, also used as the '__file__' global at runtime.  This prevents an import problem caused by the fix to #1074.

Wait 10 seconds to reload page after a restart.  On slower machines or machines with large databases, Zope can take a long time to restart and when the meta-refresh comes back before the server is up, it raises a browser error.  People who know what it does won't wait, and bumping up the timeout will help mitigate a FA
Q on the Zope lists and in the collector from those who don't.

attribute on databases.

   which is way too small with 4 lines. Increased it to 8 lines.

     - The DateTime module did not recognize the settings for
       "datetime-format".

settings from zope.conf. Because getConfiguration().datetime_format
can be expensive we provide a method getDefaultDateFormat() that
cache the value once retrieved from the configuration machinery.
Ugly (as the DateTime module) but it works.

Removing the import and call allows the tests to pass.

This code is a complete mystery.  It wasn't failing when I ran the
tests yesterday.  But if I do a checkout -D "yesterday," it fails with
an error on the Zope.startup() call.  It looks like that code should
have always failed.  No idea how it ever worked.

that these tests can fail for bogus reasons.  Jeremy saw them failing
today, and it took a while to figure out that this had nothing to do with
the ZODB changes he was making.

We'd like to deprecate explanation manipulation of a Persistent
object's _p_jar attribute.  Also use less obscure _p_deactivate()
call.

Revise comments and add assertions that object is stored and ghosted.

you to use scripts which require arguments under zopectl run.

If you do "zopectl run scriptname.py arg1 arg2", the value of sys.argv within the script will consist of ['scriptname.py', 'arg1', 'arg2'].

test_monitor_factory_with_emergency_user:  Two more that failed on
Windows, and still do, but later now.

and still fail, but later now.

but fails later now.

way it failed on Windows, only to uncover another way it fails on Windows.

        self.assertEqual(factory.host, '')

test to something else failing in

        self.check_prepare(factory)

The failure now is check_prepare's

   self.assertEqual(factory.host, "127.0.0.1")

factory.host is actually 'localhost' on Windows, but I don't understand
this test so am stopping now (and it still fails on Windows).

Add support for persistent weak references.  The implementation is in
pure Python right now; coptimizations.c was disabled.  We need to
restore the C code before going to beta.

The persistent reference format has evolved a little, but the code on
the branch doesn't document it.  The ref is usually a an oid-class
pair, where the class is an actual class object.  It can also be a
list, for weak references, or a bare oid.

Add support for data managers written against the ZODB4 transaction
API.  The transaction implementation provides an adapter between the
two interfaces.  There's a substantial doctest test suite for this
feature.

Add add() method to Connection to explicitly add an object and get it
an assigned _p_oid.  It's possible to add an unconnected object; this
isn't recommended, because it will be lost at pack time.