Current limitations:
-No way to assign different keys to different inputs. (No sure if worth the trouble implementing)
-No detecting if a key is used multiple times. What will most likely happen is that one of actions will be executed.
-Depending on what was previously assigned, xbmc might execute the old action i background when pressing the new key to assign.

With the update I can confirm that it works very well. I can also confirm that the issue is Python compatibility with XBMC's internal 2.6, since I've already updated to Python 2.7 on my copy of OS X ;)

I can also confirm it is working great(W7). I did have a problem when mapping the wrong function and trying to clear it.(kept getting a script error) I had a copy of my keyboard.XML file so I was able to go back, any way to add a backup/restore? I was wondering how many options would be available to map keys, and when I got into the menus I was a little overwhelmed(looks like a lot of keys are redundant/unused though)

I tried it and it's really cool, should be there in the settings by default. Ned, is this something that could be pushed?

One feature that I couldn't find "System.LogOff", I used to map this to one button to switch between my two libraries. Now I've mapped to XBMC restart, but it's not quite the same and takes a bit more time. There could be an option to manually add something.

It tried this this morning on a Pivos Linux and set the 'OK' to pause/play. After I did this the 'OK' wouldn't work to access anything even on the home screen. How do I restore the button? Can I delete the keymap folder in userdata and restart the box?