code to use setattr rather thah class-dictionary modifications.

followed by a security check.

by Dieter Maurer.  This was to allow storing class-defined permission
requirements for class-defined attributes in classes totally
independently from the values being protected.

necessitated by changes in the security policy that requires access to
source objects and attribute names to check acces to objects obtained
through attribute access.

necessitated by changes in the security policy that requires access to
source objects and attribute names to check acces to objects obtained
through attribute access.

New-style class dictionaries are immutable. Changed some class-update
code to use setattr rather thah class-dictionary modifications.

roles when role-computation isn't triggered through attribute accesses.

Temporarily disabled C permision-role implementation.

equivalent of the same. This was necessitated by changes in the
security policy that requires access to source objects and attribute
names to check acces to objects obtained through attribute access.

New-style class dictionaries are immutable. Changed some class-update
code to use setattr rather thah class-dictionary modifications.

The new implementation is provided as a collection of individual
packages, corresponding to the original extension modules.

(Jeremy and Tim) Changed the implementation of ZODB no lon-longer
depend on ExtensionClass.

except that 'Z' is still allowed in front of a '+/-HH:MM' timezone.  I
left that in since it was used elsewhere in the code, and was probably
harmless, whereas the other parse problems caused dates like "2003-2-5"
to be accepted as valid and silently converted into "2003-01-01".

Also re-exposed the DateTime-specific exceptions as attributes of the
DateTime class.  During their recent converted from strings to classes,
they were removed.

     - AccessControl.User used a misleading string exeception,
       'NotImplemented', which shadowed the Python builtin.