==================
- Make ``TransactionLoop`` place its transaction manager in explicit
mode. This can be faster and is easier to reason about, but forbids
the called handler from manually calling ``begin()``, ``abort()`` or
``commit()``. See `issue 20
<https://github.com/NextThought/nti.transactions/issues/20>`_.
- Move ``transaction.begin()`` out of the block of code that is
retried. Previously, an error there would probably be raised
*anyway* and not retried, unless a subclass had made customizations.
- Add ``setUp`` and ``tearDown`` methods to TransactionLoop to give
subclasses a place to hook into the inners of the transaction loop.
This is particularly helpful if they need to do something after the
transaction manager has been put in explicit mode. See `issue 22
<https://github.com/NextThought/nti.transactions/issues/22>`_.