diff test/test_mailgw.py @ 524:dce4c75bef5a

changed all config accesses... ...so they access either the instance or the config attriubute on the db. This means that all config is obtained from instance_config instead of the mish-mash of classes. This will make switching to a ConfigParser setup easier too, I hope. At a minimum, this makes migration a _little_ easier (a lot easier in the 0.5.0 switch, I hope!)
author Richard Jones <richard@users.sourceforge.net>
date Mon, 14 Jan 2002 02:20:15 +0000
parents f2edf460b0b9
children a69dc91643e9
line wrap: on
line diff
--- a/test/test_mailgw.py	Sun Jan 13 08:03:53 2002 +0000
+++ b/test/test_mailgw.py	Mon Jan 14 02:20:15 2002 +0000
@@ -8,7 +8,7 @@
 # but WITHOUT ANY WARRANTY; without even the implied warranty of
 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 #
-# $Id: test_mailgw.py,v 1.2 2002-01-11 23:22:29 richard Exp $
+# $Id: test_mailgw.py,v 1.3 2002-01-14 02:20:15 richard Exp $
 
 import unittest, cStringIO, tempfile, os, shutil, errno, imp, sys
 
@@ -73,7 +73,7 @@
 ''')
         handler = self.instance.MailGW(self.instance, self.db)
         # TODO: fix the damn config - this is apalling
-        self.instance.IssueClass.MESSAGES_TO_AUTHOR = 'yes'
+        self.db.config.MESSAGES_TO_AUTHOR = 'yes'
         handler.main(message)
 
         self.assertEqual(open(os.environ['SENDMAILDEBUG']).read(),
@@ -188,6 +188,14 @@
 
 #
 # $Log: not supported by cvs2svn $
+# Revision 1.2  2002/01/11 23:22:29  richard
+#  . #502437 ] rogue reactor and unittest
+#    in short, the nosy reactor was modifying the nosy list. That code had
+#    been there for a long time, and I suspsect it was there because we
+#    weren't generating the nosy list correctly in other places of the code.
+#    We're now doing that, so the nosy-modifying code can go away from the
+#    nosy reactor.
+#
 # Revision 1.1  2002/01/02 02:31:38  richard
 # Sorry for the huge checkin message - I was only intending to implement #496356
 # but I found a number of places where things had been broken by transactions:

Roundup Issue Tracker: http://roundup-tracker.org/