[Python] Unable to run IDLE from 2.3?

Works for me, on Win2000. I've never used XP, but I'd suggest:

*) opening a command-prompt box
*) cd'ing to %PYTHON_HOME%\lib\idlelib
(where PYTHON_HOME=C:\python23 unless changed at install time)
*) ..\..\python idle.py

watch out for error messages, and let us know...

Hi Bernard,

Well, yes, it seems there is a problem. Having followed your
instructions, I get the following error(s):

C:\Python23\Lib\idlelib>..\..\python idle.py
Traceback (most recent call last):
File "idle.py", line 23, in ?
idlelib.PyShell.main()
File "C:\Python23\lib\idlelib\PyShell.py", line 1264, in main
root = Tk(className="Idle")
File "C:\Python23\lib\lib-tk\Tkinter.py", line 1564, in __init__
self.tk = _tkinter.create(screenName, baseName, className)
_tkinter.TclError: Can't find a usable init.tcl in the following
directories:
{c:\program files\ruby\tcl\lib\tcl8.3} {c:\program
files\ruby\tcl\lib\tcl8.3} {c:/program files/ruby/tcl/lib/tcl8.4}
C:/Pytho
n23/lib/tcl8.4 C:/lib/tcl8.4 C:/library

c:/program files/ruby/tcl/lib/tcl8.3/init.tcl: version conflict for
package "Tcl": have 8.4, need 8.3
version conflict for package "Tcl": have 8.4, need 8.3
while executing
"package require -exact Tcl 8.3"
(file "c:/program files/ruby/tcl/lib/tcl8.3/init.tcl" line 19)
invoked from within
"source {c:/program files/ruby/tcl/lib/tcl8.3/init.tcl}"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list source $tclfile]"
c:/program files/ruby/tcl/lib/tcl8.3/init.tcl: version conflict for
package "Tcl": have 8.4, need 8.3
version conflict for package "Tcl": have 8.4, need 8.3
while executing
"package require -exact Tcl 8.3"
(file "c:/program files/ruby/tcl/lib/tcl8.3/init.tcl" line 19)
invoked from within
"source {c:/program files/ruby/tcl/lib/tcl8.3/init.tcl}"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list source $tclfile]"


This probably means that Tcl wasn't installed properly.

It appears the fact that I also have ruby installed is causing the
problem? Should I uninstall ruby, do you think, and try re-installing
python? I'd prefer to have access to both of them, but Python is the
language I want to concentrate on at present.

Thank you for your help!

Much warmth,

Murray
http://www.planetthoughtful.org
Building a thoughtful planet,
one snide comment at a time...

I seem to recall ruby defines tcl/tk related environment variables
which may interfere with python. If you are not using ruby-tk,
I don't think you need to de-install but merely un-defining those
variables should correct the situation. I think that's what I did
long ago so I don't see those variable names myself, and can't
be more specific....

HTH,

Bernard.

Hi Bernard,

Worked perfectly!

Removed the ruby variables and now IDLE is running! Thank you to you
(and also to the others that replied) for your help!

Much warmth,

Murray
http://www.planetthoughtful.org
Building a thoughtful planet,
one snide comment at a time...

<posted & mailed>

M Wells wrote:
There are two known causes for this bug:

-- you installed Python in a directory with a space in its path

Workaround: uninstall it, install it again in a directory with
no spaces in its path, e.g. its default C:\Python23

-- you are running a "personal firewall" that is set to inhibit
connections to host 127.0.0.1

Workaround: remove your "personal firewall" or at least reprogram
it so that connections to 127.0.0.1 are allowed; 127.0.0.1 in
TCP/IP means "this very host, me, myself" and therefore there is
no way in which connections to this address can put you at risk.

IDLE 1.0 uses sockets for communication between the 'main' process
and a secondary process that's set up to run code being developed,
and some misprogrammed 'personal firewalls' are known to interfere
with this. In theory, it is conceivable that a bad installation
of "networking" on some Windows machine might cause the same
effect as a misconfigured 'personal firewall', but so far in each
case I've analyzed it did boil down to 'personal firewalls'.


It's not necessarily the case that your troubles come from either
of these known causes, but please check both of them -- if it's
something else again, we'll need to root around for it.


Alex

[M Wells]
In addition to the two possible causes Alex spelled out, another common
problem is some *other* program setting up Tcl or Tk environment variables
pointing to an inappropriate version of Tcl/Tk. The installer for Ruby is
the most common culprit for this problem, so if you've installed Ruby that's
probably the cause.

To check, open up a DOS box and try this:

C:\Python23>python
Python 2.3 (#46, Jul 29 2003, 09:29:04) [MSC v.1200 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

I'm battling what seems to be a related issue on RH 9 (accursed Red Hat!). I
installed 2.3 from src tarball last week, and it worked fine. The new Idle
is very sexy. Yay, idle.

Then last night I decided to upgrade from RH 8 to RH 9 (accursed Red Hat!).
That was a disaster on many fronts (it's not a good thing to have corrup CD
media on the 3rd disc of a KRUD update...argh!), but it also totally trashed
my 2.3's _tkinter.so. Now when I try to rebuild 2.3 from src, I can't seem
to get a _tkinter.so which points to valid tcl & tk libraries (despite using
"--with-libs="" to point to the libtcl & libtk RH 9 installed).

(The extent of my dynamic library fu on Linux is to futz around with
symlinks from the places where _tkinter.so wants to find tcl/tk libs to the
places where they actually are on my RH 9 (accursed Red Hat!) system, then
to rerun /sbin/ldconfig. This "trick" didn't work either.)

So I decided that RH is completely evil (accursed Red Hat!), and I would
just install Tk & Tcl from scratch in /usr/local/lib and rebuild 2.3 using
those libs, like this:

./configure --with-libs="/usr/local/lib/libtcl8.4.so \
/usr/local/lib/libtk8.4.so"

This works, but goddam what a pain in my ass...In case it's now clear by
now: I hate Red Hat (though hitting back at SCO is pretty cool, trying to
keep up with Python on a RH box has been way too painful for far too long).

I recommend repeated playings, at max volume, of Bob Dylan's "Idiot Wind" if
you have to fight this battle -- it seemed to help my mood.

Kendall Clark

Do you have any form of "personal firewall" software? There is a known
issue when Idle is used with a (misconfigured) firewall. The problem
is that Idle relies on an internal socket connection. If the firewall
is set to block that socket, Idle won't start. There should be no need
to block traffic to IP address 127.0.0.1 (the local machine) so the
firewall settings should be changed to allow this.

For a better explanation, see http://www.python.org/2.3/bugs.html

Hope this helps,
Paul.