-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 12, 2007, at 2:14 PM, Brad Knowles wrote:
> At 1:03 PM -0600 2/12/07, Brad Knowles wrote:
>
>> Use the latest version of 2.4.x. As you've demonstrated, the 2.5
>> stuff is not yet fully baked, and Mailman 2.1.8 and earlier are not
>> compat
The esteemed Brad Knowles has said:
>
> Use the latest version of 2.4.x. As you've demonstrated, the 2.5
> stuff is not yet fully baked, and Mailman 2.1.8 and earlier are not
> compatible with it. $DEITY-only-knows what else they're going to
> break in the process of trying to "fix" 2.5.
>
>
At 1:03 PM -0600 2/12/07, Brad Knowles wrote:
> Use the latest version of 2.4.x. As you've demonstrated, the 2.5
> stuff is not yet fully baked, and Mailman 2.1.8 and earlier are not
> compatible with it. $DEITY-only-knows what else they're going to
> break in the process of trying to "fix"
At 10:51 AM -0700 2/12/07, [EMAIL PROTECTED] wrote:
> I was aware, when I downloaded the Mailman 2.1.9 sources, that the
> recommended Python is given as 2.4.3.
That recommendation may be a little old.
> A trip to the Python site
> showed that 2.4.4 was
Now that I've got Mailman up and running relatively smoothly in
"production" mode, I've taken some time to revisit questions primarily
involving Python. The Mailman installation I am running has several
non-standard lashups and workarounds that really need some cleanup,
and Mark Sapiro has convinc
