Seizure
commented
2 months ago We've already figured out a happy medium between "dumb", hard-coded driver loading, and a full-fledged plugin system - setting the appropriate environment variable prevents the lib from trying to check the OS and loading a compatible driver; allowing a library user to create and insert their own custom driver
current method requires setting environment variable (not a bad thing, more advanced solution could still use this) that simply skips loading of any OS-specific driver in as "VCP", and instead loads in vcp_abc as "ABCVCP" for implementation. Perhaps there's a way to insert a custom driver into pyddc to be loaded under the "VCP" name in its own namespace?