This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: IDLE fails on startup on Mac 10.5 for 2.6b3 and 3.0b3
Type: crash Stage:
Components: IDLE Versions: Python 3.0, Python 2.6
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: MLModel, gpolo
Priority: normal Keywords:

Created on 2008-09-13 04:15 by MLModel, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
unnamed MLModel, 2008-09-15 14:13
Messages (4)
msg73166 - (view) Author: Mitchell Model (MLModel) Date: 2008-09-13 04:15
IDLE fails to start on my MacBook [OS 10.5, v2.6b3 and v3.0b3, built
from source].  At the call to delete in the backtrace below index1 is 1
and index2 is 'end'.

python2.6 lib/python2.6/idlelib/
Traceback (most recent call last):
  File "lib/python2.6/idlelib/", line 21, in <module>
  File "/usrlocal/lib/python2.6/idlelib/", line 1396, in main
    shell = flist.open_shell()
  File "/usrlocal/lib/python2.6/idlelib/", line 275, in open_shell
    self.pyshell = PyShell(self)
  File "/usrlocal/lib/python2.6/idlelib/", line 816, in __init__
    OutputWindow.__init__(self, flist, None, None)
  File "/usrlocal/lib/python2.6/idlelib/", line 16, in
    EditorWindow.__init__(self, *args)
  File "/usrlocal/lib/python2.6/idlelib/", line 234, in
  File "/usrlocal/lib/python2.6/idlelib/", line 763, in
    menu.delete(1, END)  # clear, and rebuild:
  File "/usrlocal/lib/python2.6/lib-tk/", line 2665, in delete
    for i in range(self.index(index1), self.index(index2)+1):
TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'
msg73180 - (view) Author: Guilherme Polo (gpolo) * (Python committer) Date: 2008-09-13 13:06
This bug was fixed after b3 was released (r65971). You should retry it
using python 2.6rc1 or update your sources for py3k.
msg73263 - (view) Author: Mitchell Model (MLModel) Date: 2008-09-15 14:13
Theis the first time I've submitted bug reports to's 
development efforts, though I've been using Python for many years.  I 
don't know what the procedures are for followup to emails like you 
sent me, and given that the address is, I'm 
not even sure who -- if anyone -- reads a response like this.  Please 
tell me how to follow up and anything else you'd like to suggest 
about how I could help more effectively.

I retried IDLE it with Python 2.6rc1 and  got a very helpful and 
elaborate error message about not being able to start the subprocess, 
what port it was trying to connect to, and a pointer to information 
about running it without a subprocess.  I had my Mac's Security 
Firewall set to allow all incoming connections, so I don't know why 
it was refusing this one, but I changed the settings to "Set access 
for specific services and applications" and added idle26 and idle30. 
IDLE 2.6rc1 now works.

However, I checked out 3.0 sources from the Subversion repository 
yesterday, but am still getting a problem, though a different one, 
with IDLE30:

Traceback (most recent call last):
   File "<string>", line 1, in <module>
   File "/usrlocal/lib/python3.0/idlelib/", line 76, in main
AttributeError: 'Thread' object has no attribute 'set_daemon'

Should I just assume that the development problem will be taking care 
of things like this, or is it helpful for me to report them when I 
encounter them?

Thanks for your response.

	--- Mitchell

>Guilherme Polo <> added the comment:
>This bug was fixed after b3 was released (r65971). You should retry it
>using python 2.6rc1 or update your sources for py3k.
>nosy: +gpolo
>resolution:  -> out of date
>status: open -> closed
>Python tracker <>
msg73264 - (view) Author: Guilherme Polo (gpolo) * (Python committer) Date: 2008-09-15 14:58
The people in the nose list will receive emails each time a message is
sent to the issue.

Now back to your new problem.. the new problem you are reporting here
has been discussed at (where you will
find a solution).

And your final question.. It is very nice if people report any problems
they find, they all will be noticed but some will receive more attention
than others. In your specific bug report, it happened to be already
fixed in the current development version so I just sent a "standard
message". So, finishing up, it is always good to search for issues that
may be the one you are reporting so duplicates are not created.
Sometimes you won't be able to find them, that is fine, but if you find
one be sure to add something to it (if you have something to add) or
don't create a duplicate.

Sorry if this response is too dry.
Date User Action Args
2022-04-11 14:56:39adminsetgithub: 48106
2008-09-15 14:58:08gpolosetmessages: + msg73264
2008-09-15 14:13:22MLModelsetfiles: + unnamed
messages: + msg73263
2008-09-13 13:06:39gpolosetstatus: open -> closed
resolution: out of date
messages: + msg73180
nosy: + gpolo
2008-09-13 04:15:18MLModelcreate