On 2000.09.14, in <14784.29856.537110.212157@anthem.concentric.net>, "Barry A. Warsaw" <bwarsaw@beopen.com> wrote:
If you edit mm_cfg.py instead of Default.py, any errors will of course, still cause a traceback. But the proper traceback will show up in the web page as opposed to getting hidden by the missing import of VERSION. That makes it much easier for you to spot the problem and fix it. In that case, the patch isn't necessary.
Right, my argument is that this is not so in the case that you *do* edit Defaults.py -- and it doesn't seem harmful if you don't.
I still claim the site admin should never edit Defaults.py. Why do you disagree?
I'm building packages for use with multiple [virtual] servers. I make most changes in mm_cfg.py, but a) some changes should affect all servers b) some changes are dependent on the software installation, not just on the site's list preferences c) some changes (the paths at the end) depend on other settings, and changing them in every mm_cfg.py file is *messy*.
I think of Defaults.py as the set of defaults for this build of the software, not just a canonical reference of what's settable. I don't set site information there, but I do set build/installation information. Requiring this knowledge of someone installing a pre-packaged copy is unnecessary.
So, the short answer is that I'm not doing it as the site admin, so we agree. :)
-- -D. dgc@uchicago.edu NSIT University of Chicago