Brian Keegan added the comment:
I moved the idlerc to the disabled folder like you recommended and I
haven't been able to reproduce the error again. I'll cautiously take this
as an indication of a fix, but will update if it changes.
Thank you!
On Tue, Oct 9, 2012 at 2:40 PM, Ned Deily rep...@bugs.python.org wrote:
Ned Deily added the comment:
I've not seen any reports of this behavior before. Can you try two
things? One, try temporarily disabling your current IDLE preferences. Quit
IDLE, then from a terminal shell, type something like:
mv ~/.idlerc ~/.idlerc-disabled
then launch IDLE and try the paren again. If that doesn't help, try
temporarily disabling the ActiveState Tk. Again, quit IDLE. Then, from a
terminal shell:
cd /Library/Frameworks
sudo mv Tcl.framework Tcl-disabled
sudo mv Tk.framework Tk-disabled
Then try IDLE again.
--
nosy: +ned.deily
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16177
___
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16177
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com