David Meier djme...@gmail.com 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
David Meier djme...@gmail.com 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
New submission from David Meier djme...@gmail.com:
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
David Meier djme...@gmail.com 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
