On Fri, 2001-08-31 at 23:24, John W Baxter wrote:
> Most of us should do this sort of thing in mm_cfg.py (which survives
> upgrades, unlike Defaults.py). Nigel, I'm sure you have a good reason for
> saying Defaults.py, because you're very good at this stuff. Is this,
> perhaps, a setting which can't be overridden in mm_cfg.py?
Its just a case of I don't actually fiddle with these bits very often,
so got it wrong...
[And I have installed the last 5 versions from the same tree patched up,
so have not been affected by Defaults.py changes :-( ]
Nigel.
