Seth, Thanks for the quick response. I am still hoping for a clean solution to the problem. > python 2.3 does break some of those packages. > Especially b/c the path changes :) 1) Sorry to be whining, but I thought hardcoding a path is not good programming practice. At the console, when I type just "python", I get python 2.2. Is there a good reason for hardcoding the path? 2) Would it be possible to install python 2.3, and keep python 2.2 for packages with hard-coded paths? Thanks, Rick --- yum-request@xxxxxxxxxxxxxxxxxxxx wrote: > Unless Python 2.3 breaks those packages (which I think > is unlikely), I thought I should be able to upgrade > Python to a newer version without this kind of > objection. python 2.3 does break some of those packages. Especially b/c the path changes :) /usr/lib/python2.2 vs /usr/lib/python2.3 -sv
