Please, please, PLEASE generate HTML docs for PyUSB.

The useability of pydoc is complete crap compared to a web page - With a web page, I can easily have multiple tabs open to different sections of the documentation, there is an actual navigation interface, etc... While PyDoc works, it's minimal at best, and straight out of the 80's at worst.

PyDoc can [natively generate somewhat ugly, but q

Appears to be a python3.7 package installation problem?
ubuntu 18.04 LTS
python3.7
glasgow repo cloned today

After following the install instructions I try to run glasgow and get the following:

480s:2000: cd ~/.local/bin/
T480s:2001: ./glasgow 
Traceback (most recent call last):
  File "./glasgow", line 11, in <module>
    load_entry_point('glasgow', 'console_scripts', 'glasgow')

A simple wiring diagram would be great, for either the servo wiring harness or the breadboard option (where the documentation states the RPi doesn't have enough 5v sources to drive all 3 servos).
Thank you

There should be an FAQ in the wiki.
The closed issue contain a lot of knowledge and ways to debug issues.
I'd like to have them available in a wiki and also issue templates
which states what information is needed for debugging.

So the examples are useful for somethings but say if I want to have nested if statements or make something that generates this verilog:

reg signed [width:0] x [0:width-1];
always @(posedge clock) begin
    x[0] <= 0
end

I've found myself doing a lot of trial and error, reading the source and scouring the existing examples trying to find something that would use these cons

It would be great to be able to build this project, and/or https://github.com/langolierz/c_o_n_j_u_r/ and/or https://github.com/langolierz/ofxVideoArtTools/ outside of the ARM architecture.

The big problem, at least with conjur/the ofx addon, seems to be the OMX dependency.

Being able to build in an emulator, or VM, or docker, or something would be helpful for development times. Has anybody

to help with unit tests, be able to turn off the text on the patterns. This will provide known image for testing inputs, testing loopback, and testing outputs (like the encoder).

I can see a case for leaving some of it on, but I would prefer the option of having the same image across all everythings. The case for testing for text on an image doesn't seem worth the effort in providing a UI/A

Similar to CBOLD's ^ operator.

Instead of:
vcc << R(to=C(to=gnd))
We could have:
vcc ^ R() ^ C() ^ gnd

https://www.claudiokuenzler.com/nagios-plugins/check_esxi_hardware.php
"If no hw/vendor type was given, unknown will be used (like auto)"
In fact auto autodetects/selects a vendor name if it can, which unknown doesn't.

Also is there any reason unknown is the default rather than auto? Changing this would allow it to return more info by default (especially on HP), then you could switch to unkno