the time zone definition, only worked on Unix.

under Python 2.6

using hashlib.sha1 if available in order to avoid DeprecationWarning
under Python 2.6

under Python 2.6

The zeopack script has gotten a numner of improvements:

- Simplified command-line interface. (The old interface is still
    supported, except that support for ZEO version 1 servers has been
    dropped.)

- Multiple storages can be packed in sequence.

- This simplifies pack scheduling on servers serving multiple
      databases.

- All storages are packed to the same time.

- You can now specify a time of day to pack to.

- The script will now time out if it can't connect to s storage in
    60 seconds.

- It now has a test. :)

- Connections from old ZEO clients weren't discarded when they were
  closed causing memory to leak and invalidations to become
  increasingly expensive over time.

- The monitor server didn't correctly report the actual number of
  clients.

Moved a blob related logging message to debug level, for the case of everything working as intended.

Changed the url in the package metadata to point to PyPi, this avoids easy_install querying eight zope.org pages before finding the download. Also removed references to download.zope.org.

  Packing could return spurious errors due to errors notifying
  disconnected clients of new database size statistics.

  Packing a blob-enabled file storage in a ZEO server caused blob data
  to be lost.

special cases involving undo of undo of undo of object additions.

connections unused after the given time interval should be garbage
colection.  This will provide a means of dealing with extra
connections that are created in rare circumstances and that would
consume an unreasonable amount of memory.

tended to cause the same connection(s) to be used over and over.
For example, the most used conection would typically be the onlyt
connection used.  In some rare situations, extra connections could
be opened and end up on the top of the stack, causing extreme memory
wastage.  Now, when connections are placed on the stack, they sink
below existing connections that have more active objects.

quick verification of ZEO clients less than a given age even if the
number of transactions the client hasn't seen exceeds the
invalidation queue size. This is only recommended if the storage
being served  supports effecient iteration from a point near the end
of the transaction history.

Also refactored ZEO/tests/zeoserver and ZEO/runzeo to have the test
server use, and this exercisem, the option-handling code from runzeo.

abstraction to make the code a little more readable while trying to
decipher the storage locking logic.

iteratng from a starting transaction near the end of the file, the
iterator will scan backward from the end of the file to find the
starting point.