the _p_jar attributes set.

attribute.  The ownership code must take this into account.

A moment of silence, please.

in order to comply with nested scopes rules.

All Zope process will respond to signals in the specified manner:

  SIGHUP -  close open database connections and sockets, then restart the
            process

  SIGTERM - close open database connections and sockets, then shut down.

  SIGINT  - same as SIGTERM

  SIGUSR2 - rotate all Zope log files (z2.log, event log, detailed log)

The common idiom for doing automated logfile rotation will become:

kill -USR2 `cat /path/to/var/z2.pid`

The common idiom for doing "prophylactic" restarts will become:

kill -HUP `cat /path/to/var/z2.pid`

When a process is interrupted via ctrl-C or via a TERM signal (INT, TERM),
all open database connections and sockets will be closed before
the process dies.  This will speed up restart time for sites that
use a FileStorage as its index will be written to the filesystem before
shutdown.

Unspecified signals kill the process without doing cleanup.

- minor source code cleanup

The only API change was the removal of the getVocabulary method from ZCatalog.
Old-style TextIndexes can now acquire a Vocabulary from anywhere.
No Indexes, metadata or vocabulary objects are created automatically by ZCatalog.

Collector #376.

As a result of this checkin:

 - a new permission 'Copy or Move' will be registered for all classes
   that inherit from OFS.CopySupport.CopySource.  This includes
   almost all Zope objects, as SimpleItem inherits from CopySource.

 - the new permission will be granted to the Anonymous and Manager
   roles by default.

 - Site managers may choose to disallow copying of objects by
   revoking the Copy or Move permission respective to a role in
   a place or globally.

Notes:

The methods cb_isCopyable and cb_isMoveable are coopted for this
duty, although access control was never in their job description
prior to this patch.

Moved _Attribute.py module back to Attribute.py at Jim's behest in the name of maintaining similarity with the Zope 3 Interface package.

Removing mysterious setup of new objects' _p_jar in __setitem__.  I'm really not sure why it was there.  Hopefully I won't find out in production. ;-)

When an object is initialized with null bytes, do not overwrite the
PyObject_HEAD or PyObject_VAR_HEAD, which is initialized by Python
core function, e.g. PyObject_NEW().

New function EC_NewObject() is called for all object creations --
replacing four calls to either PyObject_NEW() or PyObject_NEW_VAR().
The new function initializes all the bytes that ExtensionClass is
resposible for and INCREFs the base class.

In ALLOC_FREE() macro, call _Py_NewReference() for objects allocated
from the free list.

ExtensionClass.

caused attributes to be missed with more than one level of inheritence.

withLengths to pass the new verifyClass tests.

  Because the "old" Interface package allowed the import of the Attribute
  class directly from the Interface package, and some packages
  (such as CMF) expect a class back from "from Interface import Attribute":

  - Renamed Attribute.py to _Attribute.py and did the necessary
    housekeeping to make sure all the other parts of the Interface
    package knows about the change.

  - Changed __init__.py to import Attribute from _Attribute

New features and changes:

  - Removed iclass.py  (it was no longer used).

  - Gave the base interface class (Interface._InterfaceClass) a __hash__
    method as ExtensionClass instances do not hash like normal
    instances, and we require that interfaces be hashable in order to
    store them as dictionary keys and whatnot in registries.

disappeared from the Interface package.  What replaces it?