Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Terry Reedy Newsgroups: comp.lang.python Subject: Re: IDLE quits unexpectedly when about to open or creat a new file Date: Tue, 10 Nov 2015 12:49:19 -0500 Lines: 47 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.uni-berlin.de Fwe8Op/ln+e7QwLzt/gUqQIedEkPoci44Zp4liPyzDnQ== Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.003 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'subject:IDLE': 0.04; 'subject:file': 0.07; 'instance.': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subclass': 0.09; 'unexpected': 0.09; 'python': 0.10; 'jan': 0.11; 'editorwindow': 0.16; 'general.': 0.16; 'received:80.91.229.3': 0.16; 'received:io': 0.16; 'received:plane.gmane.org': 0.16; 'received:psf.io': 0.16; 'reedy': 0.16; 'started?': 0.16; 'subject:when': 0.16; 'version?': 0.16; 'wrote:': 0.16; 'shell': 0.18; 'windows': 0.20; '2015': 0.20; 'suggested': 0.20; 'please?': 0.22; 'problem:': 0.22; 'text,': 0.22; 'am,': 0.23; 'select': 0.23; 'this:': 0.23; 'header :In-Reply-To:1': 0.24; 'sort': 0.25; 'install': 0.25; 'header :User-Agent:1': 0.26; 'command': 0.26; 'header:X-Complaints-To:1': 0.26; 'chris': 0.26; 'error': 0.27; 'idea': 0.28; 'helpful.': 0.29; "i'm": 0.30; 'window': 0.30; 'option': 0.31; 'possibly': 0.32; 'run': 0.33; 'problem': 0.33; 'message.': 0.33; 'hopefully': 0.33; 'idle': 0.33; 'lets': 0.33; 'open': 0.33; 'tue,': 0.34; 'running': 0.34; 'could': 0.35; 'nov': 0.35; 'something': 0.35; 'problem.': 0.35; 'but': 0.36; 'should': 0.36; 'possible': 0.36; 'to:addr:python-list': 0.36; 'pm,': 0.36; 'subject:: ': 0.37; 'received:org': 0.37; 'version': 0.38; 'delete': 0.38; 'stuff': 0.38; 'anything': 0.38; 'sure': 0.39; 'system.': 0.39; 'skip:e 20': 0.39; 'to:addr:python.org': 0.40; 'some': 0.40; 'your': 0.60; 'press': 0.61; 'caused': 0.61; 'back': 0.62; 'is.': 0.63; 'please,': 0.63; 'information': 0.63; 'below.': 0.66; 'research,': 0.76; 'sounds': 0.76; 'prompt': 0.79; '8.1': 0.84; 'quits.': 0.84; 'recognize.': 0.84; 'window,': 0.84; 'received:fios.verizon.net': 0.91 X-Injected-Via-Gmane: http://gmane.org/ X-Gmane-NNTP-Posting-Host: pool-173-59-124-74.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 In-Reply-To: X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com comp.lang.python:98605 On 11/10/2015 6:01 AM, Chris Angelico wrote: > On Tue, Nov 10, 2015 at 9:46 PM, wrote: >> I need help to find out what's going on. I did some research, but I couldn't find anything to solve this problem: >> >> - I open the IDLE program; From the Start menu icon, let us presume. >> - I go to the 'File' menu; Of the shell window, I presume. >> - I select the 'New File' option This should create an empty EditorWindow instance. >> - IDLE quits. Puzzling. The shell window is a subclass of EditorWindow, so EditorWindow.__init__ has already run once -- without the extra stuff added by the subclass. >> I run the IDLE version 3.3.3 on Windows 8.1 Pro. >> Should I install the most recent version? That would be a good idea in general. But first try what Chris suggested below. I am about half sure that the specific problem is on your system. It is possible that you need to delete something in HOMEDIR/.idlerc/ but lets see what the error message is. Have you been using IDLE a while, or just started? > That sounds like a very interesting problem. Can you try running it > from the command line, please? I'm not sure how to open one up from > Win 8, but it should be in the Start menu somewhere, or possibly press > Windows+R and type "cmd". With that up, type this: > > python -m idlelib.idle > > That should open up the same IDLE window that you know and recognize. > Do the exact same thing that caused the unexpected termination, and > then you should go back to the command prompt - hopefully with some > sort of error message. Copy and paste that message (as text, please, > not an image) into an email; that information could be very helpful. -- Terry Jan Reedy