I tried to assign a new key(lctrl+lshift instead of lctrl+F5) for run-
mode in option in v.2.5.2. I tried the new key and it didn't work. And 
then I got lots of messages.
So I killed the IDLE and the rest of python. And run IDLE again, 
background process indicates some activity for 5secs. And then it was 
gone. No IDLE window showed up. 
So I uninstalled the 2.5.2. and installed the v.3.1.1. The installation 
process went ok, but when I starts IDLE. Nothing happens.
I tried and run idle.py in cmd, while I'm a vista user and got this:

Traceback (most recent call last):
  File "C:\Python31\Lib\idlelib\idle.py", line 11, in <module>
    idlelib.PyShell.main()
  File "C:\Python31\Lib\idlelib\PyShell.py", line 1388, in main
    shell = flist.open_shell()
  File "C:\Python31\Lib\idlelib\PyShell.py", line 277, in open_shell
    self.pyshell = PyShell(self)
  File "C:\Python31\Lib\idlelib\PyShell.py", line 813, in __init__
    OutputWindow.__init__(self, flist, None, None)
  File "C:\Python31\Lib\idlelib\OutputWindow.py", line 16, in __init__
    EditorWindow.__init__(self, *args)
  File "C:\Python31\Lib\idlelib\EditorWindow.py", line 135, in __init__
    self.apply_bindings()
  File "C:\Python31\Lib\idlelib\EditorWindow.py", line 961, in 
apply_bindings
    text.event_add(event, *keylist)
  File "C:\Python31\Lib\idlelib\MultiCall.py", line 359, in event_add
    widget.event_add(self, virtual, seq)
  File "C:\Python31\Lib\tkinter\__init__.py", line 1353, in event_add
    self.tk.call(args)
_tkinter.TclError: bad event type or keysym "Shift"

What do I do to get this up and running?

- find your .idlerc directory (probably in %USERPROFILE%)
- edit config-extensions.cfg
- remove the <Control-Shift> binding

- write a patch that refuses invalid keysims.

Here is a patch that changes IDLE to refuse invalid key bindings.

Thanks for the help.

I removed that external row and now it's up and running again :D May I 
please have an explanation on what causes that behavior and why that 
solution on that file worked?

I'm just a n00b/beginner level on programming and I will someday try to 
understand that patch, how I can write that patch and put it in place to 
make it work.

Thank you very much for the help and guidance.

Please, understand that the bug tracker is a place to provide help and
not to seek for help. The c.l.p newsgroup (more on
http://www.python.org/community/lists/) is a more appropriate place to
continue this discussion.

Nevertheless, the attached patch was generated from python trunk so if
you want to apply it by hand you will need to check what file it changed
(first lines on it) and then check line offsets (@@ ... @@) to know
where to hand-apply each hunk. Applying any patch this way may cause
more trouble than anything else, be careful.

#21519 also patched key validation

I believe patch for #21519 affects area of file patched here.

Patch mostly looks good.  To apply now, keybindingDialog.py must become config_key.py.  I have no idea what other merge issues there might be.  The name of the new function'KeySequenceCheck()' should be 'sequence_ok()'.  A minimal new test should call sequence_ok with invalid sequence '<Control-Shift>' and valid sequence '<Control-Shift-Key-x>'.

I've made a PR for the patch.

Even though other tests need to be added, I only added a test for the call to sequence_ok().  Testing this by itself will probably allow it to be mocked in other tests.

I also added a call to the unittest in config_key.py.

New changeset 8c78aa70c888a370af18896a72cabd00e4120f09 by terryjreedy (csabella) in branch 'master':
bpo-6739: IDLE: Check for valid keybinding in config_keys (#2377)
https://github.com/python/cpython/commit/8c78aa70c888a370af18896a72cabd00e4120f09

New changeset 64a0c266e78c6b5363668012fa7fb614f6018930 by terryjreedy in branch '3.6':
[3.6] bpo-6739: IDLE: Check for valid keybinding in config_keys (GH-2377) (#2397)
https://github.com/python/cpython/commit/64a0c266e78c6b5363668012fa7fb614f6018930

Guilherme, thank you for the patch.  Sorry it took so long to be applied.  Cheryl, thank you for making the PR.  Writing invalid, exception-raising sequences to user config files was a definite bug.

stage: test needed -> resolved

messages: + msg91866
versions: + Python 2.6, Python 2.7, Python 3.2

messages: + msg91863
versions: + Python 2.5, - Python 2.6, Python 2.7, Python 3.2

messages: + msg91830

keywords: + patch

messages: + msg91812
stage: needs patch