|
|
Log in / Subscribe / Register

GNU Mailman 3.0 released

[Posted April 28, 2015 by n8willis]

From:  Barry Warsaw <barry-AT-python.org>
To:  <python-announce-list-AT-python.org>
Subject:  ANNOUNCING: GNU Mailman 3.0
Date:  Tue, 28 Apr 2015 18:20:54 -0400
Message-ID:  <20150428182054.72c86f47@limelight.wooz.org>

I am very happy to announce the release of GNU Mailman 3.0.

Over seven years in development, Mailman 3 represents a major new version,
redesigned as a suite of cooperating components which can be used to mix and
match however you want.  The core engine is now backed by a relational
database and exposes its functionality to other components via an
administrative REST+JSON API.

Our new web user interface, Postorius is Django-based, as is our new archiver
HyperKitty.  The core requires Python 3.4 while Postorius and HyperKitty
require Python 2.7.

We also have a library called mailman.client, which works in both Python 2 and
3 and is the official Python bindings to the core's REST API.  The mailman-
bundler is a set of scripts that help building out a complete Mailman 3 system
in Python virtual environments.

There are tons of new features.  See the detailed official announcement at

https://mail.python.org/pipermail/mailman-announce/2015-A...

What is GNU Mailman?

GNU Mailman is free software for managing electronic mail discussion and
e-newsletter lists.  Mailman is integrated with the web, making it easy for
users to manage their accounts and for list owners to administer their lists.
Mailman supports built-in archiving, automatic bounce processing, content
filtering, digest delivery, and more.  Mailman 3 is released under the terms
of the GNU General Public License, version 3.

See the release notes, as well as links to download each component:

    http://wiki.list.org/Mailman3


You probably want to start with the bundler and let it grab and install all
the other parts.

More information is available at:

    http://www.list.org

    http://wiki.list.org

    http://launchpad.net/mailman

    #mailman on freenode
    mailman-developers@python.org

Happy Mailman Day,
-The Mailman Cabal
Abhilash, Aurélien, Barry, Florian, John, Mark, Stephen, Sumana, and Terri
-- 
https://mail.python.org/mailman/listinfo/python-announce-...

        Support the Python Software Foundation:
        http://www.python.org/psf/donations/

to post comments

GNU Mailman 3.0 released

Posted Apr 29, 2015 2:46 UTC (Wed) by jcm (subscriber, #18262) [Link] (1 responses)

Hmmmm...it's Mailman Day in 3 days (1st of month). Who's feeling lucky? :)

GNU Mailman 3.0 released

Posted Apr 30, 2015 7:46 UTC (Thu) by rhertzog (subscriber, #4671) [Link]

From the list of features:
* All passwords hashed by default, and no monthly password reminders!

=> there's no mailman day anymore!

GNU Mailman 3.0 released

Posted Apr 29, 2015 14:13 UTC (Wed) by vivo (subscriber, #48315) [Link] (9 responses)

Could someone elaborate on this?

"The core requires Python 3.4 while Postorius and HyperKitty require Python 2.7"

has been a WTF moment reading it

GNU Mailman 3.0 released

Posted Apr 29, 2015 15:12 UTC (Wed) by kigurai (guest, #85475) [Link] (8 responses)

I'm guessing the archiving service (Hyperkitty) and the mailman delivery service are two different things and might not even have to be on the same machine.
Thus having different requirements on Python version is not that strange.

GNU Mailman 3.0 released

Posted Apr 29, 2015 19:07 UTC (Wed) by bronson (subscriber, #4806) [Link] (7 responses)

No stranger than the current Python 3 strangeness maybe. It's certainly strange.

GNU Mailman 3.0 released

Posted Apr 29, 2015 22:22 UTC (Wed) by khim (subscriber, #9252) [Link] (6 responses)

Why is it strange? Python2 and Python3 are two different langauges with no forward OR backward compatibility. Noone is surprised when some package requires use of both C and C++ compiler, why Python2 and Python3 must be treated differently?

GNU Mailman 3.0 released

Posted Apr 30, 2015 11:59 UTC (Thu) by niner (guest, #26151) [Link] (1 responses)

Most C code can actually be compiled with a C++ compiler. While Python 2 and Python 3 (or was it Python 3000?) may actually be two different languages, I certainly have never seen anyone in the Python camp admitting this. They usually claim Python to be one language. From www.python.org: "Python is a programming language that lets you work quickly and integrate systems more effectively."

Ironically, while Perl 5 and Perl 6 are different languages and this is being communicated openly (they're called "sister langauges"), it _is_ quite possible to combine Perl 5 and Perl 6 code in an application.

For the first release of a complete rewrite of an application to require both the current version of a language and a version that has been obsoleted more than 5 years ago is somewhat bizarre.

GNU Mailman 3.0 released

Posted May 1, 2015 0:34 UTC (Fri) by drag (guest, #31333) [Link]

Bringing perl 5->6 up as some sort of example for the python3 devs to learn from is probably not the best idea. I think that the only time anybody is likely to run into perl6 in the wild is from perl6 features that were backported into newer perl5 releases.

GNU Mailman 3.0 released

Posted Apr 30, 2015 16:49 UTC (Thu) by suy (guest, #81959) [Link] (3 responses)

Python2 and Python3 are two different langauges with no forward OR backward compatibility.

This is a large strech. I'm using daily Python programs that are written with compatibility in mind, in a way that work with both Python 2 and Python 3. Both versions of the language share codebases, contributors, community, BDFL, etc. Much more than C and C++ share, because those two are actually different languages, even though one branched from a certain version of the other.

GNU Mailman 3.0 released

Posted Apr 30, 2015 18:06 UTC (Thu) by mstone_ (subscriber, #66309) [Link] (2 responses)

So those programs are actually written to a third language, the portable subset of perl 2 and perl 3.

GNU Mailman 3.0 released

Posted Apr 30, 2015 18:07 UTC (Thu) by mstone_ (subscriber, #66309) [Link]

s/perl/python/

GNU Mailman 3.0 released

Posted May 1, 2015 0:23 UTC (Fri) by drag (guest, #31333) [Link]

Something like that.

In practice it's pretty trivial. I use ipython/eply/jedi/pylint with emacs on my desktop with python3 'pvenv' environment to write code that most of the time gets executed on Redhat 6-era systems. The biggest problems I run into, besides RH6 having ancient dependencies, is just remembering to use () with print.

GNU Mailman 3.0 released

Posted Apr 30, 2015 15:21 UTC (Thu) by LightDot (guest, #73140) [Link] (1 responses)

First and foremost, thanks for Mailman, it's used/abused/subscribed/unsubscribed/administered/integrated by god knows how many people, me included, and greatly appreciated.

Now for some constructive criticism (er... rant?): the rewrite to python 3.4+ was merged very late, in Dec 2014, well into the beta releases (between beta 4 and 5?).

I never ever heard of a project completely changing a programming language it is written in during the *beta*. Just don't call it a beta if you intend to drop a bomb like this, so people don't make deployment plans and program various integrations just to refactor chunks of it a bit later :) Also, I unintentionally scared my cat when I first heard of the rewrite, so there you go :)

And lastly, thanks for Mailman again. Seriously. It's a great peace of software.

GNU Mailman 3.0 released

Posted Apr 30, 2015 18:15 UTC (Thu) by LightDot (guest, #73140) [Link]

s/peace/piece


Copyright © 2015, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds