Hi all.
I'm having problems running a Quixote application that I wrote years ago on a
new machine.  I've tried lots of things and what it seems to be pointing to is
that enable_ptl interacts badly with easy_install.

My new machine is running RHEL5, I installed Python 2.5.1 and easy_install
(from setuptools 0.6c5) and Quixote 2.5b1.  My particular app is using
SQLobject and MySQLdb but for demo purposes I chose a random small package
from cheeseshop.  This is what I get:

$ python
>>> from quixote import enable_ptl
>>> enable_ptl()
>>> import munepy
Traceback (most recent call last):
  File "", line 1, in ?
ImportError: No module named munepy
>>>

versus
$ python
>>> import munepy
>>>

I tried also with Python 2.4.4 and Quixote 2.4 and get the same results.

I have Python installed under my home directory but I've done that for years
and have never had any problems.  Old machine was RHEL4, Pythone 2.4.1 and
Quixote 2.4.  Although the old machine does have a couple of easy_install eggs,
one of which is used in my application I'd rather not experiment on a working
system.

I know that in the past some modules need to be imported before the
enable_ptl() but this seems to require digging out every possible import and
not really practical.

How about not using easy_install then?  Well some s/w seems to only come as
eggs now (including the ones I need obviously).

I'd really prefer not to go back to the config of the old machine because I
have a rare opportunity to install and familiarise myself with the new s/w
*before* the old machine dies rather than try to do it in a panic.

Any suggestions?

Eddie