hi, the main issue is compiling with the same configure options as the system python. It's unlikely that all the development packages required are installed. For example, perhaps you don't have the zlib development packages installed -- so various pieces of python will end up broken.
Also, it's likely that python will be installed to /usr/local/ instead by default. This could cause issues with the incorrect python being called dependant on the path. With linux, it's usually best to use system packages for python -- so things are upgraded nicely for you automatically. Remember that the package maintainer is your friend* :) Having said all that... using linux makes building from source very easy... so it's nice to learn about it, and mess around with python from source. Check out the ./configure --help options. Definitely back up first, and do lots of reading before you do it. cu, On Tue, Jan 27, 2009 at 6:25 PM, Lenard Lindstrom <[email protected]> wrote: > Minor Python versions are simply bug fixes. Python 2.5.4 libraries are > intended as drop-in replacements for those of 2.5.2. Extension modules > compiled and linked against 2.5.2 will also work with 2.5.4. So unless Linux > version control is so finicky as to operate on the minor version level it > should be possible to uninstall 2.5.2 and install 2.5.4 in its place. > > Lenard. > > René Dudfield wrote: >> >> yes it will break packages >> >> >> On Tue, Jan 27, 2009 at 2:23 PM, Yanom Mobis <[email protected]> wrote: >> >>> >>> is it possible to install python2.5.4 on top of 2.5.2 ( ./configure && >>> make && sudo make install ) >>> on Linux? >>> >>> Will this break any packages? >>> >>> >>> >>> >>> >>> > >
