|
Size: 1014
Comment: updated version info.
|
← Revision 4 as of 2014-07-01 14:31:52 ⇥
Size: 1315
Comment: Added note about crontab and init.d.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DOC/versions/17891643 | #pragma page-filename DOC/versions/4030630 |
| Line 23: | Line 23: |
| Even after configuring Mailman with --with-python and installing it, if you are upgrading an existing installation, you may have commands in Mailman's crontab and/or an init script in /etc/init.d/mailman that reference the wrong python so you need to check for these and fix them as required.<<BR>> |
5.9. Adding a second version of Python to a server
You need to have Python 2.4 or better for Mailman - but what if you can't upgrade your python because it will break other dependencies? Install an additional version of Python, and point to it in your Mailman configure statement. Python 2.7.7 is recommended as of the writing of this FAQ, check for current recommendation and alter as needed.
# wget http://www.python.org/ftp/python/2.7.7/Python-2.7.7.tgz # tar xvzf Python-2.7.7.tgz # cd Python-2.7.7 # ./configure # make # make altinstall
The altinstall gives you a new version of Python without messing with the old one(s).
Python2.7 is now at /usr/local/bin/python2.7 Your configure statement will then include:
# ./configure --with-mail-gid=mail --with-python=/usr/local/bin/python2.7
Even after configuring Mailman with --with-python and installing it, if you are upgrading an existing installation, you may have commands in Mailman's crontab and/or an init script in /etc/init.d/mailman that reference the wrong python so you need to check for these and fix them as required.
Converted from the Mailman FAQ Wizard
This is one of many Frequently Asked Questions.