Best practice for Zope-private copy of Python 2.1 on Linux?
With the RH7.3 release today, the default Python2 installation is that much more likely to be Python 2.2 (it's the base package in RH7.3), instead of Python 2.1. Rather than ask the FAQ of why and what parts of Zope can't handle Python 2.2, I'll ask if there is, or suggest if there isn't, a shift due in the installation procedures on Linux to optionally use a private copy of Python 2.1, much like the Windows version of Zope does. That version allows me to use Python 2.2 without any interference. I'd prefer that the file layout matched WinZope as closely as possible. In this case, I'm willing to give up some disk space to have a sandbox that Zope can run in with its configuration uninterrupted. FWIW, I'd like to see an expanded tarball of Zope available that builds the whole thing, including its own Python and the most common c-extensions, in a unified makefile. Maybe that would get the possibility of RPM releases back on track, too. Can anyone suggest a best practice to get Zope 2.5.1 on Linux running with a private Python2.1, keeping the new Python releases separate from the one Zope will use?
Compile python from source with --prefix=/your/privat/python/directory and install it there. Then run the standard Zope installation process with this new Python. That's it. -aj ----- Original Message ----- From: "Jeff Kowalczyk" <jtk@adelphia.net> To: <zope-dev@zope.org> Sent: Monday, May 06, 2002 15:44 Subject: [Zope-dev] Best practice for Zope-private copy of Python 2.1 on Linux?
With the RH7.3 release today, the default Python2 installation is that much more likely to be Python 2.2 (it's the base package in RH7.3), instead of Python 2.1.
Rather than ask the FAQ of why and what parts of Zope can't handle Python 2.2, I'll ask if there is, or suggest if there isn't, a shift due in the installation procedures on Linux to optionally use a private copy of Python 2.1, much like the Windows version of Zope does. That version allows me to use Python 2.2 without any interference. I'd prefer that the file layout matched WinZope as closely as possible. In this case, I'm willing to give up some disk space to have a sandbox that Zope can run in with its configuration uninterrupted.
FWIW, I'd like to see an expanded tarball of Zope available that builds the whole thing, including its own Python and the most common c-extensions, in a unified makefile. Maybe that would get the possibility of RPM releases back on track, too.
Can anyone suggest a best practice to get Zope 2.5.1 on Linux running with a private Python2.1, keeping the new Python releases separate from the one Zope will use?
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
On Mon, 2002-05-06 at 16:51, Andreas Jung wrote:
Compile python from source with --prefix=/your/privat/python/directory and install it there. Then run the standard Zope installation process with this new Python. That's it.
I'd go one step further and suggest that you compile python with --prefix=/path/to/your/Zope, this way you end up with something that looks remarkably like the binary Zope distributed at Zope.org -- Ideas don't stay in some minds very long because they don't like solitary confinement.
On Mon, 6 May 2002, Jeff Kowalczyk wrote:
Python 2.2, I'll ask if there is, or suggest if there isn't, a shift due in the installation procedures on Linux to optionally use a private copy of Python 2.1, much like the Windows version of Zope does. That version
Personally, I just do a 'make altinstall' on my python2.1, and then install Zope using the python2.1 command. That way, python2.1 is available for any other package on my system that might need the older python version. I don't really see any benefit, myself, to giving zope a private copy. --RDM
participants (4)
-
Andreas Jung -
Jeff Kowalczyk -
Leonardo Rochael Almeida -
R. David Murray