and replaced with a ustring property

Two new methods have been added to WebDAV resources, "manage_DAVget"
and "listDAVObjects". These are now used by WebDAV instead of the
earlier "manage_FTPget" and "objectValues". This separates the
permissions, and allows WebDAV specific overriding of these methods.

Make 'publisher-profile-file' configuration file setting work.  Note that the environment variable "PROFILE_PUBLISHER" has been banished with this change.  We also change the core of Publish.py to not conditionally define functions in order to have a bit more control over the process.

- rearranged order

     - Collector #951: DateTime(None) is now equal to DateTime()

     - Collector #951: DateTime(None) now raises a proper SyntaxError

       in the Zope Book.

flattenInterfaces now walks recursivly into tuples. Tuples are used if the __implements__ declaration is like (IFoo.__implements__, IBar)

some Zope products.

- Fixed BaseRequest's traversal loop. (Collector #1079)

Fix after namespace issue fix.  Because 'action' always exists in a manage_options entry for an item, its existence in the entry is not a reliable indicator that the entry is not the "View" tab.  Since it was tested for by "has_key", the View tab always pointed back to the current page (manage_workspace).  We fix it here by using "get" instead of "has_key".

Revert feature of never updaing metadata if index is specified in catalog_object.  This broke several applications.  Instead, we provide the catalog_object method (and the Catalog.py's catalogObject method) with an update_metadata keyword argument.  If the update_metadata keyword argument is set false (the default is true), metadata is not updated.

Merge 'dont-update-metadata' fix from 2.6 branch.  When the caller specifies that only a particular set of indexes should be updated, don't update the object metadata unconditionally.

This unifies the convention in templates, scripts, and Zope 3.

'default' are still fully escaped.

without an emergency user (the original test was failing; now we're
more thorough)

caught by pychecker

In the past, if you ran an appserver as ZEO client with a persistent
cache, the startup logic prevented products from being loaded.  This
was a hack that got baked in via the weird interaction between the
FORCE_PRODUCT_LOAD and ZEO_CLIENT environment variables and was carried
over into Zope 2.7 by inertia.  Now they have nothing to do with each other
and can be specified independently.

dynamic attribute values as well as static values.