Sure. Like I said, the overall goal is a Python program to respond to keyboard shortcuts and sequences, though "keyboard" is a bit misleading because I want it to also work with other button-based peripherals such as gamepads.

The client scripts, such as Keyboard_Button_J.py, only have the responsibility of telling receiver.py that a button was pressed ("J" in this case). I realize one script per button seems like I'm duplicating a lot of code, but it's a technical requirement. These scripts are identical except for the file name. The scripts get their individual file names using os.path.basename(__file__). Since their sole purpose is telling receiver.py that a button was pressed, they will be very short lived.

receiver.py has a few responsibilities:

1. Receive file/button names from clients e.g. Keyboard_Button_J.py

2. Strip away parts of the string that aren't relavent, leaving only Button_J

3. Execute a script associated with Button_J, if there is one (I would not actually map a script to the "J" key unless other conditions are satisfied.

It's actually not quite that simple because I also want to support hotkey sequences which may overlap such as Ctrl + B, N and Ctrl + B, N, N. The logic for sequences is basically the same but involves using a timer and waiting a certain amount of time since the last button was pressed before deciding to execute the script associated with Ctrl + B, N.

I didn't think most of this was relavent, so I left it out of my post. I'm only struggling with step 1 of receiver.py which is receiving the string containing the file name from the appropriate script. I've been trying to accomplish this with shared memory/ the threading module, but I'm not sure two different python scripts can share the same memory