Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #40225 > unrolled thread

Having problems crashing IDLE

Back to article view | Back to comp.lang.python

Contents

  Having problems crashing IDLE Quintessence <quintessenceanx@gmail.com> - 2013-02-28 21:14 -0800
    Re: Having problems crashing IDLE Peter Otten <__peter__@web.de> - 2013-03-01 09:00 +0100
      Re: Having problems crashing IDLE Quintessence <quintessenceanx@gmail.com> - 2013-03-01 19:03 -0800
        Re: Having problems crashing IDLE Peter Otten <__peter__@web.de> - 2013-03-02 10:09 +0100
      Re: Having problems crashing IDLE Quintessence <quintessenceanx@gmail.com> - 2013-03-01 19:03 -0800

#40225 — Having problems crashing IDLE

I've been learning Python over the past week or so and I keep running into an issue where opening saved files will crash IDLE (not consistently, sometimes the same files with no changes will open and sometimes not). I was originally running Python 3.2.3, but I removed it and upgraded to 3.3.0 hoping to resolve the issue (but to no avail). While troubleshooting, someone suggested I try opening IDLE via command prompt. When I do that IDLE never crashes, but It does show this error (screenshot):
http://i.imgur.com/1JqiRsY.png (3.2.3)
http://i.imgur.com/5KxE88K.png (3.3.0)


Some additional info:
- When IDLE crashes it does not display an error, every open window simply closes.
- IDLE has never crashed after opening a file when I open it via command prompt, even if it was previously consistently displaying that behavior.
- I am running Windows 7 x64 with all updates.

Has anyone ever encountered this? What does the error mean?

[toc] | [next] | [standalone]

#40233

Quintessence wrote:

> I've been learning Python over the past week or so and I keep running into
> an issue where opening saved files will crash IDLE (not consistently,
> sometimes the same files with no changes will open and sometimes not). I
> was originally running Python 3.2.3, but I removed it and upgraded to
> 3.3.0 hoping to resolve the issue (but to no avail). While
> troubleshooting, someone suggested I try opening IDLE via command prompt.
> When I do that IDLE never crashes, but It does show this error
> (screenshot): http://i.imgur.com/1JqiRsY.png (3.2.3)
> http://i.imgur.com/5KxE88K.png (3.3.0)

Your posts are easier to deal with if you provide tracebacks as text. 
Here's what I get:

Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/local/lib/python3.3/tkinter/__init__.py", line 1442, in 
__call__
    return self.func(*args)
  File "/usr/local/lib/python3.3/idlelib/MultiCall.py", line 174, in handler
    doafterhandler.pop()()
  File "/usr/local/lib/python3.3/idlelib/MultiCall.py", line 221, in 
<lambda>
    doit = lambda: self.bindedfuncs[triplet[2]][triplet[0]].remove(func)
ValueError: list.remove(x): x not in list

> Some additional info:
> - When IDLE crashes it does not display an error, every open window simply
> closes. - IDLE has never crashed after opening a file when I open it via
> command prompt, even if it was previously consistently displaying that
> behavior. - I am running Windows 7 x64 with all updates.
> 
> Has anyone ever encountered this? What does the error mean?

This looks like the following bug:

http://bugs.python.org/issue8900

You might be able to work around it by selecting the

"At Startup Open Shell Window" option under

Options-->Configure IDLE-->General-->Startup Preferences

[toc] | [prev] | [next] | [standalone]

#40315

Thank you for the advice! I checked the setting you specified and "Open Shell Window" at startup was already selected. Is there another bug this could be related to?

Thank you!

On Friday, March 1, 2013 3:00:40 AM UTC-5, Peter Otten wrote:
> Quintessence wrote:
> 
> 
> 
> > I've been learning Python over the past week or so and I keep running into
> 
> > an issue where opening saved files will crash IDLE (not consistently,
> 
> > sometimes the same files with no changes will open and sometimes not). I
> 
> > was originally running Python 3.2.3, but I removed it and upgraded to
> 
> > 3.3.0 hoping to resolve the issue (but to no avail). While
> 
> > troubleshooting, someone suggested I try opening IDLE via command prompt.
> 
> > When I do that IDLE never crashes, but It does show this error
> 
> > (screenshot): http://i.imgur.com/1JqiRsY.png (3.2.3)
> 
> > http://i.imgur.com/5KxE88K.png (3.3.0)
> 
> 
> 
> Your posts are easier to deal with if you provide tracebacks as text. 
> 
> Here's what I get:
> 
> 
> 
> Exception in Tkinter callback
> 
> Traceback (most recent call last):
> 
>   File "/usr/local/lib/python3.3/tkinter/__init__.py", line 1442, in 
> 
> __call__
> 
>     return self.func(*args)
> 
>   File "/usr/local/lib/python3.3/idlelib/MultiCall.py", line 174, in handler
> 
>     doafterhandler.pop()()
> 
>   File "/usr/local/lib/python3.3/idlelib/MultiCall.py", line 221, in 
> 
> <lambda>
> 
>     doit = lambda: self.bindedfuncs[triplet[2]][triplet[0]].remove(func)
> 
> ValueError: list.remove(x): x not in list
> 
> 
> 
> > Some additional info:
> 
> > - When IDLE crashes it does not display an error, every open window simply
> 
> > closes. - IDLE has never crashed after opening a file when I open it via
> 
> > command prompt, even if it was previously consistently displaying that
> 
> > behavior. - I am running Windows 7 x64 with all updates.
> 
> > 
> 
> > Has anyone ever encountered this? What does the error mean?
> 
> 
> 
> This looks like the following bug:
> 
> 
> 
> http://bugs.python.org/issue8900
> 
> 
> 
> You might be able to work around it by selecting the
> 
> 
> 
> "At Startup Open Shell Window" option under
> 
> 
> 
> Options-->Configure IDLE-->General-->Startup Preferences

[toc] | [prev] | [next] | [standalone]

#40328

Quintessence wrote:

> Thank you for the advice! I checked the setting you specified and "Open
> Shell Window" at startup was already selected. Is there another bug this
> could be related to?

None that I and google could find. Close idle and remove (or rename) the 
.idlerc directory in your home folder, and then start Idle again. 

If the problem persists it is very unlikely that it is configuration-
related. In that case I suggest that you file a bug report yourself or amend 
your observations to the existing one.

[toc] | [prev] | [next] | [standalone]

#40316

Thank you for the advice! I checked the setting you specified and "Open Shell Window" at startup was already selected. Is there another bug this could be related to?

Thank you!

On Friday, March 1, 2013 3:00:40 AM UTC-5, Peter Otten wrote:
> Quintessence wrote:
> 
> 
> 
> > I've been learning Python over the past week or so and I keep running into
> 
> > an issue where opening saved files will crash IDLE (not consistently,
> 
> > sometimes the same files with no changes will open and sometimes not). I
> 
> > was originally running Python 3.2.3, but I removed it and upgraded to
> 
> > 3.3.0 hoping to resolve the issue (but to no avail). While
> 
> > troubleshooting, someone suggested I try opening IDLE via command prompt.
> 
> > When I do that IDLE never crashes, but It does show this error
> 
> > (screenshot): http://i.imgur.com/1JqiRsY.png (3.2.3)
> 
> > http://i.imgur.com/5KxE88K.png (3.3.0)
> 
> 
> 
> Your posts are easier to deal with if you provide tracebacks as text. 
> 
> Here's what I get:
> 
> 
> 
> Exception in Tkinter callback
> 
> Traceback (most recent call last):
> 
>   File "/usr/local/lib/python3.3/tkinter/__init__.py", line 1442, in 
> 
> __call__
> 
>     return self.func(*args)
> 
>   File "/usr/local/lib/python3.3/idlelib/MultiCall.py", line 174, in handler
> 
>     doafterhandler.pop()()
> 
>   File "/usr/local/lib/python3.3/idlelib/MultiCall.py", line 221, in 
> 
> <lambda>
> 
>     doit = lambda: self.bindedfuncs[triplet[2]][triplet[0]].remove(func)
> 
> ValueError: list.remove(x): x not in list
> 
> 
> 
> > Some additional info:
> 
> > - When IDLE crashes it does not display an error, every open window simply
> 
> > closes. - IDLE has never crashed after opening a file when I open it via
> 
> > command prompt, even if it was previously consistently displaying that
> 
> > behavior. - I am running Windows 7 x64 with all updates.
> 
> > 
> 
> > Has anyone ever encountered this? What does the error mean?
> 
> 
> 
> This looks like the following bug:
> 
> 
> 
> http://bugs.python.org/issue8900
> 
> 
> 
> You might be able to work around it by selecting the
> 
> 
> 
> "At Startup Open Shell Window" option under
> 
> 
> 
> Options-->Configure IDLE-->General-->Startup Preferences

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web