keyboard

Hi! I've used your library in various projects and am very grateful for it! I figured it'd be worth a shot to ask you this here, since I just caught you: have you considered adding some support for "rehooking"/"restarting" the library, so that callees can restart your library whenever they detect that their environment has changed (e.g. input devices have been (dis)connected, etc)? I've contributed with some info to this issue https://github.com/boppreh/keyboard/issues/264 as to how we're dealing with this in some of our projects. Funnily enough, I didn't know about `python -m keyboard`, and had I known about it, it would definitely have saved me some time! Once again, thank you very much for your hard work!

I'm the author of the `keyboard`[1] library mentioned in the article. - It reads all events because it's meant to interface with your keyboard directly, for global hotkeys, macros, disabling or remaping keys, etc. Interacting with windows and per-application hotkeys are explicitly not a goal of the library at the moment. - It reads /dev/input because the library was developed to work in as many environments as possible, including headless installations like raspberry pi's that may not have a graphical environment or even a monitor. There's an open change to _try_ to communicate with the X server first and fallback to /dev/input, but event suppression is not working reliably with this yet. - It could read /dev/input by just being in the `input` group, but then `dumpkeys` doesn't work and you are stuck typing numeric scan codes instead of k

If I may plug my own free project, https://github.com/boppreh/keyboard may achieve what you want. Also note it has mouse support now; it's hidden, but exists.

A while ago I tried to use sphinx-autoapi, but the experience was simply frustrating. Too many steps, too many dependencies, the tooling required numerous tweaks to generated good output, and errors were difficult to debug. I ended up writing my own script. Now I simply do ./docstring2markdown.py modulename [github_master_url] > README.md And it generates a Markdown API like this one: https://github.com/boppreh/keyboard#api . Note it includes constants and their values, full method signatures with default values, points out aliases (methods with the same name), keeps everything in the order it was declared, and provides a link to the line number on the source. It's not perfect, but I'm quite happy for a ~100loc script. Hopefully they launch something as easy and I can retire my script.