Add missing helper functions, logging, and event reading

[Poofjunior]

Just wondering if anyone is maintaining this package. I use it frequently for siloed development of Harp-compliant devices without needed to use Bonsai.

Overall, if the option exists, I'd love to take over maintaining this package as a self-contained solution to chatting with Harp devices in python.

Monster commit summary:

• suppresses spurious print statements
• adds several missing helper functions (reading/writing Floats, etc.)
• updates package installation details.
• add primitive udev rules for FTDI-based boards (linux).
• adds python-style logging of all received messages

[Poofjunior]

@filcarv @glopesdev , @patricklatimer recently made some changes on our fork enabling us to read event messages seamlessly without altering the original API.

It would be great to get these changes merged and pushed to PyPI as this makes the package more-or-less feature-complete with interacting with reald-world devices over harp protocol in python.

[glopesdev]

@Poofjunior @patricklatimer we discussed this recently and I am happy to review and move with the initial maintenance work to merge this.

One outstanding question we have is determining the relationship between this package and harp-python.

Specifically that package is already on PyPI and we were wondering it might be very useful to unify the data API with the control API.

Alternatively we can decide on a shared top-level namespace, e.g. harp-tech.harp, deprecate the current harp-python and publish two separate packages, one with the data interface, and another with the control interface.

If we can make a note to discuss this soon and aim to have a decision by next week, I can reorganise the repository structures and cherry pick from your PR.

[MicBoucinha]

Hi, we have been following this PR and we share similar goals that the ones mentioned here.

We appreciate the long needed changes to pyharp made by @Poofjunior, @patricklatimer and @jessy-liao and we would like to invite everyone to continue this discussion on the issue opened here.

We would like to be part of the next steps of pyharp's development and we would like to know your thoughts as well. We contemplated some of the concerns mentioned by @glopesdev, namely the possibility of merging harp-python and pyharp under the same umbrella (being it coherence between namespaces used or even in the same PyPI package).

Looking forward to continue this discussion on the aforementioned issue.

Cheers!

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 3 committers have signed the CLA.

✅ Poofjunior
❌ jessy-liao
❌ patricklatimer
_{You have signed the CLA already but the status is still pending? Let us recheck it.}