Problem with mailman-2.1a1, syntax error in bin/update : print >> sys.stderr ...
Hi.
This is the error I get when I try to do a ./configure of mailman-2.1a1:
Compiling /home/mailm21/Mailman/versions.py ... File "bin/update", line 81 print >> sys.stderr, 'Fixing language templates:', mlist.internal_name() ^ SyntaxError: invalid syntax File "bin/check_perms", line 96 arg.ERRORS += 1 ^ SyntaxError: invalid syntax
I tried with python 2.0 and python 2.1b1 and same result.
Here is how I made python 2.0:
./configure make make test make altinstall
I installed mimelib 0.2 downloaded over the weekend:
python2.0 setup.py install
And verified the install as per the doc
I tried to install mailman-2.1a1 (downloaded today) with:
./configure --prefix=/home/mailm21 --with-username=mailm21 --with-groupname=mailm21 --with-python=/usr/local/bin/python2.0 --with-mail-gid=daemon
I tried with and without PYTHONPATH=/usr/local/lib/python2.0
I'm on Linux.
-- Patrick Timmons, service informatique
"PT" == Patrick Timmons <ptimmons@courriel.polymtl.ca> writes:
PT> I tried with python 2.0 and python 2.1b1 and same result.
PT> Here is how I made python 2.0:
| ./configure
| make
| make test
| make altinstallI'm not even sure what "make altinstall" does. ;) These error sure point to Mailman finding an earlier version of Python than 2.0.
-Barry
Hi.
I made a hard link to python2.0 and named it /usr/local/bin/python and it worked. Thanks.
I was under the impression that I could use option --with-python=/usr/local/bin/python2.0 with configure where /usr/local/bin/python2.0 is the python interpreter.
Is this option used to point to the directory where python is or to the executable in itself ?
"Barry A. Warsaw" wrote:
"PT" == Patrick Timmons <ptimmons@courriel.polymtl.ca> writes:
PT> I tried with python 2.0 and python 2.1b1 and same result. PT> Here is how I made python 2.0: | ./configure | make | make test | make altinstallI'm not even sure what "make altinstall" does. ;) These error sure point to Mailman finding an earlier version of Python than 2.0.
-Barry
-- Patrick Timmons, service informatique
"PT" == Patrick Timmons <ptimmons@courriel.polymtl.ca> writes:
PT> Hi.
PT> I made a hard link to python2.0 and named it
PT> /usr/local/bin/python and it worked. Thanks.
| I was under the impression that I could use option
| --with-python=/usr/local/bin/python2.0 with configure
| where /usr/local/bin/python2.0 is the python interpreter.
PT> Is this option used to point to the directory where python is
PT> or to the executable in itself ?To the executable itself, however it won't help you with the command line scripts. They pick up the first Python executable on your $PATH (this should be fixed, but requires a lot of autoconf-related changes so it's not high on my list).
-Barry
Hi Barry,
I'm not even sure what "make altinstall" does. ;) These error sure point to Mailman finding an earlier version of Python than 2.0.
Couldn't some of the make targets check that the version of Python available is sufficiently recent? This seems to crop up a lot as Mailman is using recent Python features.
Ralph.
"RC" == Ralph Corderoy <ralph@inputplus.demon.co.uk> writes:
>> I'm not even sure what "make altinstall" does. ;) These error
>> sure point to Mailman finding an earlier version of Python than
>> 2.0.
RC> Couldn't some of the make targets check that the version of
RC> Python available is sufficiently recent? This seems to crop
RC> up a lot as Mailman is using recent Python features.The configure script is supposed to enforce this, but it hadn't been updated. I've just checked in the fix for this.
-Barry
participants (3)
-
barry＠digicool.com -
Patrick Timmons -
Ralph Corderoy