You had mentioned a reference to the Django settings for HK. Even if HK is enabled, django should not get imported into the MM space.
The proper way to handle the issue of URLs would be to have the MM core query the UI for them. However, I have yet to convince Barry that the present model (where, at present, MM is the only part allowed to be authoritative over ANY information that it uses) is inappropriate. So, for the present, we need to have a proxy for the UI and a section of the configuration that specifies the values for the parameters which it supplies. IMHO, we should actually treat it as multiple proxies so that we can handle the more generic configuration in a consistent manner. On Sep 13, 2012, at 9:53 AM, Aurelien Bompard wrote: > Sorry I messed up with a list-reply, so you people missed Richard's reply. > >> What concerns me is that MM core should not depend on Django in order to run. >> The Archive interface needs to accept the message and place it in the store. > > MM won't depend on Django, only if the HK section in mailman.cfg is enabled. > I can't just send the message to the store however, since the > IArchiver interface also has methods to get the list and message's > final archive URL, and that's dependent on the frontend. The store > does not know how the frontend is installed (at the root URL, on > /hyperkitty, on /archives, etc.). > Those methods are run before the message is stored in order for their > result to be added to the message headers, so I can't even get it from > the archive_message call. > > Aurélien _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
