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.

Author brianckeegan
Recipients brianckeegan, ned.deily
Date 2012-10-09.18:55:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CALrYNy_ih-GvsQh0UJn-ZAAeGWWtioG1CyvOLd-haeBa1p-YDA@mail.gmail.com>
In-reply-to <1349808031.19.0.2298415773.issue16177@psf.upfronthosting.co.za>
Content
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 <report@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 <report@bugs.python.org>
> <http://bugs.python.org/issue16177>
> _______________________________________
>
History
Date User Action Args
2012-10-09 18:55:21brianckeegansetrecipients: + brianckeegan, ned.deily
2012-10-09 18:55:21brianckeeganlinkissue16177 messages
2012-10-09 18:55:21brianckeegancreate