of a re-index.

o The new tests are amphibious:  they exercise both the Python and the C
  implementations, ensuring that they remain in sync.

wasn't used anywhere else in the class to protect methods.

Send ContainerModifiedEvent when appropriate.

This requires Five 1.3+ >= r20254.

Some BBB has been kept until Zope 3.2 >= r40368 is stiched in.

- replaced url_quote by html_quote for hidden add value (pushing the add button escapes the value again)

nonexistent method. Removed one such method.

Fixed unclear security declarations. When bug 761 was fixed,
declareProtected(perm) was made illegal, at least one method name was
required. This checkin does the same for declarePrivate() and
declarePublic().

Also there was a bug in that a class having:
  security = ClassSecurityInfo()
  __ac_permissions__ = ((perm, ()),)
was not equivalent to a class having:
  __ac_permissions__ = ((perm, ()),)
This first form had as a buggy side effect have the behavior of
  __ac_permissions__ = ((perm, ('')),)
which is equivalent to
  __roles__ = PermissonRole(perm)
Not it will simply make the permission available from this object
(with default roles).

and Lifetime into packages.  The remaining two, Zope and ImageFile,
will clean up themselves as they're slated for removal in Zope 2.11.

  Make ++skin++ work for Five views by putting another stub method on the
  request.  I wonder when we can retire ZPublisher and use zope.publisher
  instead.

No commit message

  Name the root collection simply "Zope" so that the name of the tarball will
  be decent.  This doesn't conflict with the collection representing the 'zope'
  package because the *root* collection and a dependency of it never have to
  coexist as sibling directories somewhere; so no danger of problems due to
  case ignorant file systems.

  Only include *.py files for the scripts (in particular, DON'T include
  the ZODBTools directory which was previously caught up in the '*' glob
  and confused zpkgsetup).
  
  Also include ZODBTools scripts (again, only *.py files).

  Forgot that zope.testbrowser is actually required by zope.app. So stitch
  it back it in. Good news is that has become easier in the mean time; no
  top-level modules involved (anymore); just mechanise and ClientCookie.