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

2009-04-23 Thread Barry Finkel
I wrote, in part: Or do I have to specify something to get the Mailman-supplied e-mail package untarred? Thanks. and Mark Sapiro replied: That would be another approach. After running ./configure and before running any make commands, you could edit misc/Makefile to replace the line

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

2009-04-23 Thread Mark Sapiro
Barry Finkel wrote: My Python version is 2.4.3, and I ran a modified conftest.py program from the configure script to determine that the email package is 3.0.1. I could not determine the package version number from looking at the .py modules in /usr/lib/python2.4/email on my Ubuntu Mailman

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

2009-04-22 Thread 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

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

2009-04-22 Thread Mark Sapiro
Barry Finkel wrote: 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:

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

2009-03-16 Thread Mark Sapiro
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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