Hi Steve
On Fri, Aug 8, 2014 at 10:04 AM, Stephen J. Turnbull <
[email protected]> wrote:
> Rajeev S writes:
>
> ...
>
Sure, but that's not particularly important since actually it will be
> the mailman.client directory when you integrate it, and (especially
> after Barry's post just now)
Rajeev S writes:
> Further, The mmclient.py *should have* a callable function for it
> to work as a module entry point (a.k.a shell command), when
> installed through `python setup.py install`. The created executable
> does `import` the mmclient
I still don't understand this. You have a modu
Hi! it's been a long time since I wrote here (12 years according to my
archives!), but I've never stopped reading :)
I'm following with a lot of interest the progress of Mailman 3 (great job,
BTW), kudos to all devs, including the GSoC youngsters), and I've seen that
the Fedora infrastructure peop
Hey guys,
Do we have a web interface to get list archives?
Are they available (archives) on MM3 ?
Best,
Alex Azevedo
aazevedo
___
Mailman-Developers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/mailman-developer
On Fri, Aug 08, 2014 at 04:51:25PM -0300, Alex Azevedo wrote:
> Hey guys,
> Do we have a web interface to get list archives?
> Are they available (archives) on MM3 ?
You may be interested in the HyperKitty project:
https://fedorahosted.org/hyperkitty/
Demo instance: https://lists.stg.fedoraproje
Hi,
On Friday 08 August 2014 05:41 PM, Stephen J. Turnbull wrote:
I still don't understand this. You have a module whose "main
function" would perfectly servicable as "the executable" if you unwrap
it (delete the "def main" statement and fix indentation), and in fact
doesn't serve any purpose
