Transaction: transaction.begin() - synchronizer newTransaction() method called inconsistently

[Siddhartha Kasivajhula]

For a synchronizer, the newTransaction() method is only called when an explicit call to transaction.begin() is made, and not when a new transaction is implicitly started by a call to transaction.get(). These two cases (explicitly vs implicitly begun transactions) should be treated the same, and newTransaction() should be called in both cases.

Some comments from Jim Fulton on zodb-dev on resolution:

"
Really, ``begin` and ``abort`` are equivalent. It might be better if
there wasn't a ``begin`` method, as it's missleading. One should be an
alias for the other. I'd be for deprecating ``begin``. The call to
``_new_transaction`` should be moved to the point in ``get`` where a
new transaction is created, and ``begin`` should be made an alias for
``abort``.
"

[Jim Fulton (jim-zope)]

FTR I was wrong. :)

See: https://groups.google.com/forum/#!topic/python-transaction/dPcjNoKR_q4