Deprecation problem and ConnectionStateError, was: Re: [ZODB-Dev] Span transaction over several threads

[Tim Peters]

[Tim Peters]
>> get_transaction() should be deprecated too, BTW.

[Shane Hathaway]
> +1

Still, I haven't.  The new-in-3.3 transaction package still supplies get(),
begin(), commit() and abort() functions, all resolving to actions on an
automatically created instance of ThreadTransactionManager.  So long as
that's true too, deprecating get_transaction() seems to be pointless ("No!
You have to spell that 'get()' now instead!" "Why?" "Because the
'get_transaction()' spelling is deprecated!" "Why?" ...).

Forcing explicit use of a transaction manager would be a change with some
actual benefit for some, but would also create more work for apps that are
happy with one instance of a ThreadTransactionManager (which they get
without effort now).  AFAICT, the latter apps are still the most common
case, so making life harder for them is a strong disincentive.