-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Oct 21, 2006, at 8:29 PM, Tokio Kikuchi wrote:
> Mark Sapiro wrote: >> If the new configuration.Configuration.load() method is given a >> configuration file argument which is a non-existent file, it will >> silently fall back to loading mm_cfg.py. >> >> I think it should remember whether a filename argument is passed and >> complain if the passed file doesn't exist. >> > +1 > > BTW, should we all move to new config sheme ? Then, should we make > some > upgrade script in Mailman/versions.py ? So one question is whether we should continue to support mm_cfg.py for Mailman 2.2. Originally I thought we should for backward compatibility. Tokio, are you suggesting that we move a MM2.1 mm_cfg.py to etc/mailman.cfg during the upgrade? If we do that, then we can just eradicate mm_cfg.py altogether. Otherwise, if we decide to keep mm_cfg.py for backward compatibility, I do think we ought to complain if a file is passed in that doesn't exist. I wasn't sure we should do the complaining in .load(), but since those are only every called from bin scripts, I think that's probably fine. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRTvmenEjvBPtnXfVAQJhSgP/ZgIaDWPDCvEWecYNPgNyU3RTbqco7xp/ gycUe0kyo0MFqmuRcJd/HDYqar5JaLIPSRYhNM8b5w8OgdrL5sJGJX1eOTiuv0sb TSr2jiJHnnGIXZyNRj2Q2HDZw4yURBbrT0S8eaTtaxe2P2V0N8udmyRgfem1lynk bAREAHkUaUY= =hidD -----END PGP SIGNATURE----- _______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
