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 Ritornell
Recipients Ritornell, bg90299, terry.reedy
Date 2016-12-11.10:40:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This is a bug you'll run into whenever you set a key binding that is somehow ambiguous to IDLE and for some other reason than being already assigned (for in that case, IDLE will warn, but only then). Like when you set a binding, that would normally be interpreted by the editor for some input modification or so. I think this should be handled more gracefully or at least fail in a more informative way, esp. since beginners on Windows may not be that comfortable on the command line.

A "hard" workaround for the time being is to simply remove your config-keys.cfg file, thus resetting all bindings to their default. On Windows this is usually located in your .idlerc directory in C:\Users\YourName\. You might also edit this file by hand and just remove the offending binding, although that assumes you know which one it is, of course.
Date User Action Args
2016-12-11 10:40:12Ritornellsetrecipients: + Ritornell, terry.reedy, bg90299
2016-12-11 10:40:12Ritornellsetmessageid: <>
2016-12-11 10:40:12Ritornelllinkissue28711 messages
2016-12-11 10:40:11Ritornellcreate