[Mailman-Users] Mailman 2.1.12 - Python 2.4.[456] incompatibility

[Barry Finkel]

On Mon, 16 Mar 2009 10:52:05 Mark Sapiro wrote:

>There is an internal inconsistency in the 3.0.2 email package that
>shipped with Python 2.4.4 through 2.4.6. This has to do with the
>Charset.Charset() constructor setting input_charset to a unicode which
>then causes TypeError: decoding Unicode is not supported exceptions in
>other parts of the email package. This problem does not seem to occur
>with email 3.0.1 and Python 2.4.[123].
>
>This (along with other stuff) is discussed in the bug report at
><https://bugs.launchpad.net/mailman/+bug/328353> and there is a patch
>for email/Charset.py at
><http://launchpadlibrarian.net/23670138/Charset.py.patch>
>
>At this point, the best advice seems to be use Python 2.5 or 2.6 with
>Mailman 2.1.12.

The patch is to module Charset.py.  I was looking for that in my
2.1.12 directories, and I cannot find it.  In comparing my 2.1.11
directories with my 2.1.12 directories I find the "problem".
These directories are where I built my Ubuntu packages from the
SourceForge source.

In
     build_mailman_2.1.11/mailman-2.1.11/misc/Makefile.in

I have

     EMAILPKG=       email-2.5.8
     JACODECSPKG=    JapaneseCodecs-1.4.11
     KOCODECSPKG=    KoreanCodecs-2.0.5

and I have the same in Makefile.in . But in

     build_mailman_2.1.12/mailman-2.1.12/misc/Makefile.in

I have

     EMAILPKG=       @EMAILPKG@
     JACODECSPKG=    JapaneseCodecs-1.4.11
     KOCODECSPKG=    KoreanCodecs-2.0.5

and in Makefile.in

     EMAILPKG=       
     JACODECSPKG=    JapaneseCodecs-1.4.11
     KOCODECSPKG=    KoreanCodecs-2.0.5

As a result, I have in the misc directory for 2.1.12

     email-2.5.8.tar.gz

and that tarball was not untarred, so I do not have Charset.py .
In the build process output for 2.1.11 I see

     for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \
             do \
                 gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \
                 ...

and for 2.1.12 I see

     for p in  JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \
             do \
                 gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \
                 ...

In the 2.1.12 configure I see

# Should we rely on Python's own email package or use the pre-packaged version?

     if test "$needemailpkg" = "ok"
     then
	 EMAILPKG=""
     else
	 EMAILPKG=email-2.5.8
     fi
     echo "$as_me:$LINENO: result: $needemailpkg" >&5
     echo "${ECHO_T}$needemailpkg" >&6

and in the build output I see

     checking Python version... 2.4.3
     checking Python's email package... ok

I am confused.  Is the 2.1.12 build using the Python-supplied e-mail
library, and thus the patch to Charset.py has to be made there?
Or do I have to specify something to get the Mailman-supplied
e-mail package untarred?  Thanks.
----------------------------------------------------------------------
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory          Phone:    +1 (630) 252-7277
9700 South Cass Avenue               Facsimile:+1 (630) 252-4601
Building 222, Room D209              Internet: BSFinkel at anl.gov
Argonne, IL   60439-4828             IBMMAIL:  I1004994