Brian Thorne

It is certainly better than it was but still no, not really. It serves as a good reference for those familiar with the library. If I recall someone asked for...

Agree, needs a champion! My 2c is that `BusABC.state` should include all the options as @bggardner has suggested.

Yeah I'm also a fan of Azure, but it seems we can do almost everything with Github actions which would be marginally easier (and probably runs on Azure by now!)....

If we switched to using a PAT, what do you suggest to avoid recursive workflow runs? I'm happy to disable the format-code workflow if it is messing things up

Hmm that is annoyingly slow but I'm not sure what to do about it. Do you mind uploading the import profile? If a blank user display is the main concern...

This is a good proposal, and a clean default implementation. I also don't see how a callback would interact nicely with the backends that already offload periodic messages (without falling...

`python-can` actually implemented J1939 in the past but we deliberately made the decision to focus on raw CAN and leave higher level protocols for libraries and applications (hoping that they...

Yes as it probably effects how the docs are rendered. I'll take a look.

Here are the errors in master from the 3.1 merge: ``` /home/travis/build/hardbyte/python-can/can/interface.py:docstring of can.Bus:1: WARNING: py:class reference target not found: can.bus.BusABC /home/travis/build/hardbyte/python-can/can/bus.py:docstring of can.BusABC.send_periodic:9: WARNING: py:meth reference target not found:...

Thanks for the interest @drandreaskrueger. I have no plans to backport python-paillier at this time however I would carefully review and consider merging a pull request. As an aside, using...