Type info

[FoamyGuy]

resolves #28

I am not certain whether using Any is the best option for **kwargs but there are many different possible types of the various different arguments that can get passed that way. I tried using some of the specific types but mypy still reported errors. I'm not sure if we have another option beyond breaking out all of the possible arguments and declaring types for all of them. I'm still pretty new to typing in python though, perhaps I've overlooked something or someone else has ideas.

There is possibly something that still needs done to make the sphinx docs correct. When building locally I'm not seeing the proper arguments for init(). But strangely when I build the docs from main I'm seeing the same issue. So perhaps there is some difference in my environment vs. in actions.

I tested this driver successfully with a Raspberry Pi B+ using Blinka_Displayio

[FoamyGuy]

The latest commit removes the mock import for displayio from the sphinx conf.py file. It turned out that being mocked was causing the arguments to turn out incorrectly when building the sphinx docs locally. And it does not need to be mocked because adafruit-blinka-displayio is listed in requirements.txt which fulfills the need for displayio for sphinx to understand.

With the latest commit I am seeing proper arguments listed in a local sphinx build:

[gamblor21]

I did some looking on the types and using Any for the kwargs seems as much of a solution as anyone has right now for this type of situation. The rest looks good to me.