summaryrefslogtreecommitdiff
path: root/Mailman/Queue/CommandRunner.py
diff options
context:
space:
mode:
authorbwarsaw2002-05-02 02:54:46 +0000
committerbwarsaw2002-05-02 02:54:46 +0000
commitea909c059b1c1671adbb995d292649482277ad95 (patch)
tree183863b01c5835627d7edbf0aac6e6c2fcc1d067 /Mailman/Queue/CommandRunner.py
parent8550439af7c64c4c2a857318388be5a202dd3292 (diff)
downloadmailman-ea909c059b1c1671adbb995d292649482277ad95.tar.gz
mailman-ea909c059b1c1671adbb995d292649482277ad95.tar.zst
mailman-ea909c059b1c1671adbb995d292649482277ad95.zip
New architecture for email commands. Instead of the monolithic (and
unmaintainable) MailCommandHandler.py file, we've now got a framework where each command is implemented in a separate file. This means it's both more extensible and more flexible: - you can easily add new commands for things I haven't thought of <wink>, and the `help' command will automatically adjust - you can disable commands entirely by removing the appropriate file - you can disable, change, or add commands on a per-list (or even per-message or per-sender) basis CommandRunner.py is the module that calls into this framework. Each command is implemented as a cmd_<command>.py file. The `set' command is the most complicated. The help text is currently implemented as module docstrings (for most commands), so the i18n catalogs must be updated. Also the help.txt files will be updated.
Diffstat (limited to 'Mailman/Queue/CommandRunner.py')
0 files changed, 0 insertions, 0 deletions