[issue11068] Python 2.7.1 Idle Segmentation Fault OS X (10.6.6)

2011-01-29 Thread David Meier

New submission from David Meier :

After IDLE launches I select 'File->Open' browse to a blank .py file, when I 
select the particular file I get the segfault below...

silverbox:~ user$ (idle&)
silverbox:~ user$ Traceback (most recent call last):
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/idlelib/run.py",
 line 93, in main
seq, request = rpc.request_queue.get(block=True, timeout=0.05)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/Queue.py", 
line 177, in get
self.not_empty.wait(remaining)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", 
line 257, in wait
_sleep(delay)
TypeError: 'int' object is not callable

--
components: IDLE
messages: 127492
nosy: David.Meier
priority: normal
severity: normal
status: open
title: Python 2.7.1 Idle Segmentation Fault OS X (10.6.6)
type: crash
versions: Python 2.7

___
Python tracker 
<http://bugs.python.org/issue11068>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue11068] Python 2.7.1 Idle traceback on OS X (10.6.6)

2011-01-29 Thread David Meier

David Meier  added the comment:

It doesn't matter what's in the file itself.  By 'blank' I mean, literally, an 
empty file (i.e. `touch file.py`).

You are correct that this was installed from the 10.6 specific 2.7.1, I will 
try to install from the other version.  Is there a recommended uninstallation 
before trying this?

--

___
Python tracker 
<http://bugs.python.org/issue11068>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue11068] Python 2.7.1 Idle traceback on OS X (10.6.6)

2011-01-30 Thread David Meier

David Meier  added the comment:

Removing the 10.6 specific Python 2.7.1 installation (with the instructions 
provided by Ned) and reinstalling the 10.3-10.6 32bit installation fixed the 
aforementioned segfault.  Thanks for the information, however, I do think it 
should be noted on the download page that there are problems with the 10.6 
32/64-bit version and it is safer to go the 32-bit only installer unless there 
is a specific need.  I did not see any caveats mentioned when I went to 
download it.

--

___
Python tracker 
<http://bugs.python.org/issue11068>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue11068] Python 2.7.1 Idle traceback on OS X (10.6.6)

2011-01-31 Thread David Meier

David Meier  added the comment:

Sorry that what I had pasted in does not show a segfault, however if you run it 
as `idle` (i.e. no `(idle&)) the command line reports a generic "Segmentation 
fault" with no traceback.  So, yes, it is a segmentation fault - but I figured 
it was more useful if you had the traceback when running it that way.  Whether 
or not the two are related I do not know.

--

___
Python tracker 
<http://bugs.python.org/issue11068>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com