[Python-bugs-list] [ python-Bugs-635327 ] IDLE GUI doesn't start

noreply@sourceforge.net noreply@sourceforge.net
Fri, 08 Nov 2002 08:58:57 -0800

Bugs item #635327, was opened at 2002-11-07 20:52
You can respond by visiting: 

Category: IDLE
Group: Platform-specific
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Rachelle Moore (moorere)
Assigned to: Nobody/Anonymous (nobody)
Summary: IDLE GUI doesn't start

Initial Comment:
I downloaded the Python-2_2_2.exe self-extracting file from python.org, and successfully installed it on 

Both the IDLE GUI and command line interpreter seemed to work exactly as expected.  I eventually found 
myself using the path browser to look at many modules, and it crashed.  Being windows, this isn't an 
extraordinary event, so I simply went on to something else.  I don't remember if I stopped IDLE and tried 
to come back to it, though I tend to think I did, and that it did work.

That was yesterday.  Today, after a cold restart, the IDLE GUI doesn't come up at all, though the 
command interpreter does. 

I notice that the \Python22\Tools\idle\README.txt says in part: "IDLE requires Python 1.5.2, so it is 
currently only usable with a Python 1.5.2 distribution."  Hmm.

Thank you.
Rachelle Moore


>Comment By: Rachelle Moore (moorere)
Date: 2002-11-08 08:58

Logged In: YES 

Deleted with Win98 "add/remove programs," then deleted subdirectories themselves.  Reinstalled from the same 
copy of its self-extracting file; it still works after two cold restarts.  Yay!

Provisionally I would relate the discrepency to some sort of overflow within the path browser.  Before it first crashed 
IDLE, I had briefly opened 20-30 modules for examination, and at one point had 6-8 "Python Shell" windows open.  
(There was no previous installation of Python, unless dustbunnies can program.)  Thanks.


Comment By: Raymond Hettinger (rhettinger)
Date: 2002-11-07 21:35

Logged In: YES 

I also had an IDLE experience upon updating to 2.2.2.
The root cause turned out to be things left over in
the install directory from prior python versions.
I recommend clearing the whole directory tree
and re-installing.  If your problem goes away,
please close this bug.

The readme.txt file should really say, "Requires *at least*
python 1.5.2 *or later*".

I'll fixed the wording.


You can respond by visiting: