From 607d756e962dce912134e075dbcc5f11a91987f0 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Wed, 19 Jan 2011 21:34:19 -0500 Subject: - The ``pyramid_zodb``, ``pyramid_routesalchemy`` and ``pyramid_alchemy`` paster templates now use a default "commit veto" hook when configuring the ``repoze.tm2`` transaction manager in ``development.ini``. This prevents a transaction from being committed when the response status code is within the 400 or 500 ranges. See also http://docs.repoze.org/tm2/#using-a-commit-veto. --- TODO.txt | 3 --- 1 file changed, 3 deletions(-) (limited to 'TODO.txt') diff --git a/TODO.txt b/TODO.txt index 75dc5199f..e34c2fe55 100644 --- a/TODO.txt +++ b/TODO.txt @@ -6,9 +6,6 @@ Must-Have (before 1.0) - Write a "Whats New" (delta from BFG 1.3) -- Use a commit veto when configuring repoze.tm2 in paster templates for - non-1X, 2X, or 3X responses. - - Figure out how to slim the herd of paster templates. Related: https://github.com/Pylons/pyramid/issues#issue/40, https://github.com/Pylons/pyramid/issues#issue/42, -- cgit v1.2.3