Comment 7 for bug 113298

Scott:

1) I didn't do an *upgrade*, I did an *install*. However, after the install, I mounted my old /usr/local, and things started going wrong.

2) I think it is a *bug* in ubuntu if the system python is looking into the site-packages of another python which lives in /usr/local. Their library paths should not intermingle. They have never done so before, in ubuntu, or any other linux with which I am familiar (and I have been doing this a long time).

3) Having multiple pythons on a system is how you work out how to upgrade systems. It's ludicrous to suggest that it shouldn't be done. However, I'm obviously willing to admit I may have done it in a way that wasn't optimal, but see point 2) above ... this is not dissimilar to what would happen if you have a script which users /usr/bin/env python rather than /usr/bin/python lurking in your system ... as I say, I suspect something similar ...

How about not *rejecting* it quite yet ...