On Thu, 2004-11-25 at 16:39 -0800, Rick Graves wrote: > 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? they do that so both python 2.2 and 2.3 could be installed at the same time - but the path to site-packages (where to find the python modules from external packages) must be known. > 2) Would it be possible to install python 2.3, and > keep python 2.2 for packages with hard-coded paths? not really. this is why those items are rebuilt. -sv
