After trying to load IDLE from the interactive prompt, the problem seems to
be in 'protocol.py' when it tries to open a socket. To understand why, we
will need to consult the new IDLE Gods. IMHO, not having this turned off
by default turns IDLE from a usefull tool into a useless one (the last
thing I need is one more command-line argument to spedify).
That's just my opinion, I could be wrong.
Jon Polley
Quote:
> Hi all,
> I have installed Python 2.0, and just downloaded the
> idlefork-0.7.1.tar.gz. I unpacked it into my
> /usr/lib/python2.0/site-packages directory, and tried to start idle.py.
> The message I get is:
> "Something already has our socket, but it won't open a window for me!
> Unable to proceed."
> I see that the problem occurs in PyShell after a failed call to
> protocol.py.
> Has anyone else had this problem? The older Idle works fine.
> I am running Redhat 6.2 Linux.
> TIA,
> Glenn
> --
> Glenn R. Williams
> Director, Special Projects
> RSG Systems, Inc.