Zope.security

==================

- Use ``from`` imports instead of ``zope.deferred`` to avoid circular
import problems, thus drop dependency on ``zope.deferredimport``.

- Raise ``NoInteraction`` when ``zope.security.checkPermission`` is called
without interaction being active (LP 301565).

- Don't define security checkers for deprecated set types from the
"sets" module on Python 2.6. It's discouraged to use them and
``set`` and ``frozenset`` built-in types should be used instead.

- Change package's mailng list address to zope-dev at zope.org as
zope3-dev at zope.org is now retired.

- Remove old zpkg-related files.

==================

- Install decorated security checker support on ``LocationProxy`` from the
outside.

- Add support to bootstrap on Jython.

- Move the ``protectclass`` module from ``zope.app.security`` to this
package to reduce the number of dependencies on ``zope.app.security``.

- Move the ``<module>`` directive implementation from ``zope.app.security``
to this package.

- Move the ``<class>`` directive implementation from ``zope.app.component``
to this package.

==================

- Make C code compatible with Python 2.5 on 64bit architectures.

==================

- Add ``frozenset``, ``set``, ``reversed``, and ``sorted`` to the list of
safe builtins.

==================

- Changed title for ``zope.security.management.system_user`` to be more
presentable.

====================

- Backport a fix made by Gary Poster to the 3.4 branch:
Fix for LP bug 181833 (from Gustavo Niemeyer). Before "visiting" a
sub-object, a check should be made to ensure the object is still valid.
Because garbage collection may involve loops, if you garbage collect an
object, it is possible that the actions done on this object may modify the
state of other objects. This may cause another round of garbage collection,
eventually generating a segfault (see LP bug). The ``Py_VISIT`` macro does
the necessary checks, so it is used instead of the previous code.