From 20029d76b7eb81ffccd7312d588f500584900b15 Mon Sep 17 00:00:00 2001
From: bwarsaw
Date: Thu, 31 May 2001 15:57:23 +0000
Subject: SetUserDigest(): Do not do a self.Save() at the end of this.  I
 believe all calls to SetUserDigest() should be wrapped in the standard
 lock-munge-save-unlock fences.  If not, they should be!

This should radically improve performance when many of these calls are
made sequentially.
---
 Mailman/Digester.py | 2 --
 1 file changed, 2 deletions(-)

(limited to 'Mailman/Digester.py')

diff --git a/Mailman/Digester.py b/Mailman/Digester.py
index 08cbfea25..0d281069e 100644
--- a/Mailman/Digester.py
+++ b/Mailman/Digester.py
@@ -126,8 +126,6 @@ class Digester:
                     self.one_last_digest = {addr: self.digest_members[addr]}
 		del self.digest_members[addr]
 		self.members[addr] = cpuser
-        # BAW: This Save() can probably go away.
-	self.Save()
 
     def send_digest_now(self):
         # Note: Handler.ToDigest.send_digests() handles bumping the digest
-- 
cgit v1.2.3-70-g09d2