[Zope-dev] New ways of getting transactions?

[Jim Fulton]

Andreas Jung wrote:
> 
> 
> --On 11. Dezember 2005 12:28:04 -0500 Jim Fulton <jim at zope.com> wrote:
> 
>> Stefan H. Holek wrote:
>>
>>> import transaction
>>> transaction.get()
>>> transaction.commit()
>>> transaction.abort()
>>> transaction.savepoint()
>>>
>>> This works since 2.8, but not in 2.7. Nearly every project has come  up
>>> with its own backward compatibility module though. See for example
>>> CMFCore.utils.transaction or CMFPlone.transaction.
>>
>>
>> I'm dispayed to hear this. :(  The old use of 
>> __builtins__.get_transaction
>> should be deprecated and supported for a period of time.  If it isn't,
>> then this
> 
> 
> The deprecation warning in Zope 2.8 says:
> 
> -c:1: DeprecationWarning: This will be removed in ZODB 3.6:
>   use transaction.get() instead of get_transaction().
>   transaction.commit() is a shortcut spelling of 
> transaction.get().commit(),
>   and transaction.abort() of transaction.get().abort().
> 
> Zope 2.9 comes with ZODB 3.6. So the behaviour is correct in some way 
> but I agree that the deprecation should continue longer. It would be 
> save to remove it in Zope 2.10.

Yup.

BTW, This is a good example for why I want to start using time-based
deprecation.

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org