Jump from Python 2.4 to 2.7...
I'm going to be doing a new Mailman installation on a Red Hat Enterprise Linux (RHEL) system 5.11 with Python 2.4.3. The goal is to convert existing ListProc mailing lists to Mailman without having to change the addresses for the lists. I've done a similar conversion in the past many years ago and expect it to take a few months to get all my list owners moved to the to the new MLM.
When all the lists are eventually converted or retired, I will then migrate this new Mailman installation from the above platform to a new RHEL 7 installation with Python 2.7.
My question is, are there any quirks or gotchas that I should be aware of in going from the old RHEL/Python platform to the new one? Is there anything I can do on the old system now that will make migration to the new platform easier? For example, I could use Pythonbrew to install a private v2.7 Python on the old box for Mailman to use, rather than relying on the system's older Python.
In general is it a good practice to give Mailman it's own Python installation rather than relying on and dinking with the system's Python.
...BC
-- =====================================[ Bill.Costa@unh.edu ]== Bill Costa 1 Leavitt Lane UNH IT -- 1st Floor University of New Hampshire Durham, NH 03824 USA Voice: +1-603-862-3056 No good deed... Goes unpunished. ===========================[ http://pubpages.unh.edu/~wfc ]==
I'm going to be doing a new Mailman installation on a Red Hat Enterprise Linux (RHEL) system 5.11 with Python 2.4.3. The goal is to convert existing ListProc mailing lists to Mailman without having to change the addresses for the lists. I've done a similar conversion in the past many years ago and expect it to take a few months to get all my list owners moved to the to the new MLM.
When all the lists are eventually converted or retired, I will then migrate this new Mailman installation from the above platform to a new RHEL 7 installation with Python 2.7.
My question is, are there any quirks or gotchas that I should be aware of in going from the old RHEL/Python platform to the new one? Is there anything I can do on the old system now that will make migration to the new platform easier? For example, I could use Pythonbrew to install a private v2.7 Python on the old box for Mailman to use, rather than relying on the system's older Python.
FWIW, we're still on RHEL 5 and have been using the Python 2.7 RPMs from iuscommunityproject for several years. Here's the repo file:
[iuscommunityproject] name=IUS Community Project baseurl=http://dl.iuscommunity.org/pub/ius/stable/Redhat/5/$basearch/ enabled=1 gpgcheck=1 gpgkey=http://dl.iuscommunity.org/pub/ius/IUS-COMMUNITY-GPG-KEY
Cheers Sebastian
Sebastian Hagedorn - Weyertal 121, Zimmer 2.02 Regionales Rechenzentrum (RRZK) Universität zu Köln / Cologne University - Tel. +49-221-470-89578
On 03/02/2015 08:22 AM, Bill.Costa@unh.edu wrote:
My question is, are there any quirks or gotchas that I should be aware of in going from the old RHEL/Python platform to the new one? Is there anything I can do on the old system now that will make migration to the new platform easier? For example, I could use Pythonbrew to install a private v2.7 Python on the old box for Mailman to use, rather than relying on the system's older Python.
Are you installing Mailman 2.1.19 on the Red Hat system or using whatever Red Hat rpm package that's available, and if the latter, what is that? And, what Mailman will you be using on the RHEL 7 system?
I ask because the FAQ at <http://wiki.list.org/x/8486953> may be relevant.
Assuming you will be installing Mailman 2.1.19 from source, I would be more concerned over potential difficulties due to the older Python than with any gotchas from moving to a newer Python although there are some compatibility issues with older Mailman versions and newer Python. See <http://wiki.list.org/x/4030629> for more on both kinds.
In general is it a good practice to give Mailman it's own Python installation rather than relying on and dinking with the system's Python.
My production server is Centos 5 with Python 2.4.3, but I also have Python 2.7.9 installed and configure Mailman --with-python=/usr/bin/python2.7. I wouldn't necessarily call it "good practice", but it's certainly a viable approach.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/2/2015 9:53 AM, Mark Sapiro wrote:
On 03/02/2015 08:22 AM, Bill.Costa@unh.edu wrote:
My question is, are there any quirks or gotchas that I should be aware of in going from the old RHEL/Python platform to the new one? Is there anything I can do on the old system now that will make migration to the new platform easier? For example, I could use Pythonbrew to install a private v2.7 Python on the old box for Mailman to use, rather than relying on the system's older Python.
Are you installing Mailman 2.1.19 on the Red Hat system or using whatever Red Hat rpm package that's available, and if the latter, what is that? And, what Mailman will you be using on the RHEL 7 system?
I ask because the FAQ at <http://wiki.list.org/x/8486953> may be relevant.
Assuming you will be installing Mailman 2.1.19 from source, I would be more concerned over potential difficulties due to the older Python than with any gotchas from moving to a newer Python although there are some compatibility issues with older Mailman versions and newer Python. See <http://wiki.list.org/x/4030629> for more on both kinds.
In general is it a good practice to give Mailman it's own Python installation rather than relying on and dinking with the system's Python.
My production server is Centos 5 with Python 2.4.3, but I also have Python 2.7.9 installed and configure Mailman --with-python=/usr/bin/python2.7. I wouldn't necessarily call it "good practice", but it's certainly a viable approach.
Interesting. We moved our Mailman instance from CentOS 5.x running Mailman 2.1.9 to SLES version ? running Mailman 2.1.18-1 and python 2.7.
When we switched, the OS was some concern but the main decision we made was to use Mailman from the source at list.org and python 2.7. We have made some custom modifications here and getting Mailman from the source would allow us to upgrade Mailman a little easier than from the OS maintainer. By divorcing our Mailman instance from the version provided by the OS maintainer, we can pick up our instance and switch to a newer host easier.
Chris
Mark Sapiro <mark@msapiro.net> recently posted, in part...
Are you installing Mailman 2.1.19 on the Red Hat system or using whatever Red Hat rpm package that's available, and if the latter, what is that? And, what Mailman will you be using on the RHEL 7 system?
Well my original plan was to install the latest and greatest Mailman on both the old RHEL 5 system, and then the new RHEL 7, rather than use whatever the RPM package does.
I ask because the FAQ at <http://wiki.list.org/x/8486953> may be relevant.
It definitely is relevant. I was just asking the system admin if I should be putting the install someplace other than what was recommended in the manual and I specifically mentioned FHS issues.
Assuming you will be installing Mailman 2.1.19 from source, I would be more concerned over potential difficulties due to the older Python than with any gotchas from moving to a newer Python although there are some compatibility issues with older Mailman versions and newer Python. See <http://wiki.list.org/x/4030629> for more on both kinds.
Well that's why I thought it could avoid issues by installing the latest Python as well, just for Mailman, and leave the system Python alone.
My production server is Centos 5 with Python 2.4.3, but I also have Python 2.7.9 installed and configure Mailman --with-python=/usr/bin/python2.7. I wouldn't necessarily call it "good practice", but it's certainly a viable approach.
Thanks for the confirmation.
...BC
-- =====================================[ Bill.Costa@unh.edu ]== Bill Costa 1 Leavitt Lane UNH IT -- 1st Floor University of New Hampshire Durham, NH 03824 USA Voice: +1-603-862-3056 No good deed... Goes unpunished. ===========================[ http://pubpages.unh.edu/~wfc ]==
In a message of Mon, 02 Mar 2015 15:15:01 -0500, Bill.Costa@unh.edu writes:
Mark Sapiro <mark@msapiro.net> recently posted, in part...
Are you installing Mailman 2.1.19 on the Red Hat system or using whatever Red Hat rpm package that's available, and if the latter, what is that? And, what Mailman will you be using on the RHEL 7 system?
Well my original plan was to install the latest and greatest Mailman on both the old RHEL 5 system, and then the new RHEL 7, rather than use whatever the RPM package does.
I ask because the FAQ at <http://wiki.list.org/x/8486953> may be relevant.
It definitely is relevant. I was just asking the system admin if I should be putting the install someplace other than what was recommended in the manual and I specifically mentioned FHS issues.
Assuming you will be installing Mailman 2.1.19 from source, I would be more concerned over potential difficulties due to the older Python than with any gotchas from moving to a newer Python although there are some compatibility issues with older Mailman versions and newer Python. See <http://wiki.list.org/x/4030629> for more on both kinds.
Well that's why I thought it could avoid issues by installing the latest Python as well, just for Mailman, and leave the system Python alone.
My production server is Centos 5 with Python 2.4.3, but I also have Python 2.7.9 installed and configure Mailman --with-python=/usr/bin/python2.7. I wouldn't necessarily call it "good practice", but it's certainly a viable approach.
Thanks for the confirmation.
...BC
I have been away. I get to this discussion late, and so sorry if this has been mentioned, but
YOU ABSOLUTELY MUST NOT CHANGE YOUR CENTOS SYSTEM PYTHON 2.4.3 OR YOU WILL BREAK YOUR WHOLE PACKAGING SYSTEM!
(now I go back and read older mail. must get this warning out now.)
Laura
On 03/02/2015 01:56 PM, Laura Creighton wrote:
I have been away. I get to this discussion late, and so sorry if this has been mentioned, but
YOU ABSOLUTELY MUST NOT CHANGE YOUR CENTOS SYSTEM PYTHON 2.4.3 OR YOU WILL BREAK YOUR WHOLE PACKAGING SYSTEM!
Quite true. I found this out the hard way a long time ago. Yum depends on various other 'site-packages' modules which IIRC would not work on Python newer than 2.4.x I gave up. That's why the default Python on my CentOS 5 server is 2.4.3, even though there is a python2.7 invoking python 2.7.9 and most everything that I install that uses Python is configured to use python2.7.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Aha, I now see that you know not to replace your system Python. Sorry for the note in haste, but if you were about to do such a thing I needed to tell you NO! DON'T DO THAT! in a hurry.
Apologies, apologies ... (from somebody who only learned that about CentOS only _after_ she thought thatinstalling a more modern Python system-wide would be in everybody's interest)
Laura
Laura Creighton writes:
Apologies, apologies ... (from somebody who only learned that about CentOS only _after_ she thought thatinstalling a more modern Python system-wide would be in everybody's interest)
Yes, indeed. "Don't touch /usr/bin/python" is an ancient Red Hat and Centos bugaboo going back to Python 1.5.2 at least (never used RHEL, but since Centos suffers from it, I suppose older versions of RHEL do, too). It's interesting (not a criticism, I really mean "interesting") that you had to learn from experience, Laura.
Is this true of recent Fedora, even today?
Regards,
Steve
participants (6)
-
Bill.Costa＠unh.edu -
Chris Nulk -
Laura Creighton -
Mark Sapiro -
Sebastian Hagedorn -
Stephen J. Turnbull