Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Jim Fulton
Morten W. Petersen wrote: Hi, I'm having some code that bombs out trying to commit a transaction; I believe it's because of new ways of doing things in Zope 2.9.. how do you call the equivalents of get_transaction().commit() and abort() in Zope 2.9? Will those new ways work with Zope

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Stefan H. Holek
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.

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Jim Fulton
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

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Morten W. Petersen
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

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Andreas Jung
--On 11. Dezember 2005 17:01:56 +0100 Morten W. Petersen [EMAIL PROTECTED] wrote: Hi, I'm having some code that bombs out trying to commit a transaction; I believe it's because of new ways of doing things in Zope 2.9.. how do you call the equivalents of get_transaction().commit() and

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Andreas Jung
--On 11. Dezember 2005 12:28:04 -0500 Jim Fulton [EMAIL PROTECTED] 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

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Tim Peters
A number of ZODB gimmicks were officially deprecated in ZODB 3.4, and removed in ZODB 3.6. Zope 2.9 uses the latter. From the ZODB NEWS file for 3.6: Removal of Features Deprecated in ZODB 3.4 -- (3.6b2) ZODB 3.6 no longer contains features officially

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Jim Fulton
Andreas Jung wrote: --On 11. Dezember 2005 12:28:04 -0500 Jim Fulton [EMAIL PROTECTED] 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

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Tim Peters
[Jim Fulton] ... BTW, This is a good example for why I want to start using time-based deprecation. In a world with time-based releases, is there a difference? ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev

Re: [Zope-dev] New ways of getting transactions?

2005-12-11 Thread Jim Fulton
Tim Peters wrote: [Jim Fulton] ... BTW, This is a good example for why I want to start using time-based deprecation. In a world with time-based releases, is there a difference? Yes, because release numbers aren't very helpful when software is used by many applications. For example, I