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 Def
> "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-ev
On Tue Aug 13, 2002 at 07:43:42PM +0100, Richard Barrett wrote:
> A couple of thoughts:
>
> 1. Some list attributes are initially set from mm_cfg.py configuration
> variables ONLY when the list is created. Subsequent changes to those
> defaults aren't propagated automatically into these per lis
At 10:56 13/08/2002 -0700, Timothy R. Robnett wrote:
>On Tue Aug 13, 2002 at 10:45:19AM -0700, Bob Weissman wrote:
> > At 10:20 AM 8/13/02, you wrote:
> > >I installed MM yesterday and got it working. However changes added to
> > >mm_cfg.py do not appear to have any effect. However if I break the
On Tue Aug 13, 2002 at 10:45:19AM -0700, Bob Weissman wrote:
> At 10:20 AM 8/13/02, you wrote:
> >I installed MM yesterday and got it working. However changes added to
> >mm_cfg.py do not appear to have any effect. However if I break the rules
> >and change Defaults.py it does have the desired eff
I installed MM yesterday and got it working. However changes added to
mm_cfg.py do not appear to have any effect. However if I break the rules
and change Defaults.py it does have the desired effect. bin/check_perms
reports that everything is fine.
A search of the archives didn't yield any leads.
