At 16:01 13/08/2002 -0400, Barry A. Warsaw wrote: > >>>>> "RB" == Richard Barrett <[EMAIL PROTECTED]> writes: > > RB> fyi: all the Mailman code imports mm_cfg.py which in turn > RB> imports Defaults.py. Hence the definitions in mm_cfg.py are > RB> evaluated following evaluation of Defaults. py. Values > RB> assigned in Defaults.py are re-evaluated after mm_cfg.py is > RB> processed by Python. If changing it in Defaults.py works and > RB> changing it in mm_cfg.py does not then I reckon you've got > RB> problem 2 above.
There was a "not" omitted from this sentence. \Snetence should have read: "Values assigned in Defaults.py are NOT re-evaluated after mm_cfg.py is processed by Python." Sorry for creating any confusion. >FTR, Mailman considers mm_cfg.py off-limits w.r.t. upgrades -- it will >never touch them. However it's within Mailman's rights to overwrite >Defaults.py on installs and upgrades. That's why you should never >make changes to Defaults.py, and always make them to mm_cfg.py > >As was pointed out though, if you're making changes to list defaults, >the changes won't affect already created lists. You'll need to change >those via the web (for most list config variables) or through the >command line bin/withlist for a couple of exceptions. > >-Barry ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
