Re: [Zope-Coders] Re: SVN: Zope/trunk/lib/python/Testing/ZopeTestCase/ transaction.commit(1) is deprecated in favor of transaction.savepoint().
Thank you for the clarification, Tim. On 3. Nov 2005, at 16:22, Tim Peters wrote: The full deprecation msg spells it out in more detail: subtransactions are deprecated; instead of transaction.commit (1), use transaction.savepoint(optimistic=True) in contexts where a subtransaction abort will never occur, or sp=transaction.savepoint() if later rollback is possible and then sp.rollback() instead of transaction.abort(1) Last time *I* saw it, it said subtransactions are deprecated; use transaction.savepoint() instead of transaction.commit(1) ;-) So, either way, the current code is a bit off target. Best guess is that you're not interested in *sub*transaction aborts here, so that you do want to pass optimistic=True. This is correct. I will pass True then. Stefan -- Anything that happens, happens. --Douglas Adams ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
[Zope-Coders] Zope tests: 7 OK
Summary of messages to the zope-tests list. Period Thu Nov 3 12:01:01 2005 UTC to Fri Nov 4 12:01:01 2005 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:01:27 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003478.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:02:58 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003479.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:04:28 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003480.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:05:58 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003481.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:07:28 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003482.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:08:58 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003483.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Nov 3 22:10:28 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-November/003484.html ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
[Zope-Coders] Why zope-coders?
Do we really need this list? In theory, this list is supposed to be about repository-management issues, but that isn't what the traffic has really been about. It has occasional messages about Zope development issues and lots of output from a nightly test runner. I propose to retire this list and move the traffic over to zope-dev. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
Re: [Zope-Coders] Why zope-coders?
On 11/4/05, Jim Fulton [EMAIL PROTECTED] wrote: I propose to retire this list and move the traffic over to zope-dev. I always wondered why this was a separate list. +1 on its retirement. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Society attacks early, when the individual is helpless. --B.F. Skinner ___ Zope-Coders mailing list Zope-Coders@zope.org http://mail.zope.org/mailman/listinfo/zope-coders
