pycopy VS libudev-zero

Oh, so you're interested to get 100 tomes of technical drawings for SpaceX? You may be out of luck with it, but with any open-source project you're in luck - source to answer all of your questions is right there ;-). https://github.com/pfalcon/pycopy in this case. There's also the testsuite which formally specifies everything Pycopy can do (coverage 97%): https://github.com/pfalcon/pycopy/tree/master/tests . Finally, the docs include the section on specific differences with CPython3.4: https://pycopy.readthedocs.io/en/latest/differences/index.html (but that's human-written, so definitely not complete). By the way, docs are 381 pages rendered as a PDF: https://pycopy.readthedocs.io/_/downloads/en/latest/pdf/ .

Really? Here's direct link to the closest subsection header: https://github.com/pfalcon/pycopy/#the-unix-version , and quoting it here for you:

Well, here it is: https://github.com/pfalcon/pycopy/blob/master/py/vm.c#L367

https://github.com/pfalcon/pycopy/tree/v3.5.0 (if you prefer to drop people into the code, since the release URL does not contain release notes)

For device management with libinput integration, you have several options. First: you could install mdevd + libudev-zero and enable mdevd service. You would also want to disable default mdev and hwdrivers services with mdevd taking their place. Second: use mdev with libudev-zero and libudev-zero-helper package. In this case you would need additions to mdev.conf described here: https://github.com/illiliti/libudev-zero/blob/master/contrib/mdev.conf Third: use eudev.

you can manage yours devises in /dev with mdevd and libudev-zero