Want to use BleakClient within bleak package

I would like to have at least BleakClient available within bleak, in other words: move the platform-dependent imports from __init__.py to a new module (say api.py). __init__.py would then import them from there, but so could other modules within bleak.

If you’re willing accept a pull request for this let me know.

The reason I want this is that I’m working on a Pythonic interface to get and put values, using 2904 descriptors to marshal and unmarshal values, plus accessor classes for services and characteristics. Hopefully you’ll eventually be able to do things like

async with PythonicBleakClient(address, timeout=10) as client:
    batteryLevel = await client.services['Battery Service'].characteristics['Battery Level'].get()

But PythonicBleakClient and the accessor classes are backend-independent, and I don’t want to put all the functionality in BaseBleakClient.

[jackjansen]

I didn’t have time to work on Bleak for more than a year (which was quite a bit longer than anticipated:-), but I’m going to pick this one up again. I hope to have a pull request shortly (presuming real work doesn’t interfere again:-)

Plan is to create the _api.py with abstract classes like AbstractBleakClient, then import the machine-dependent classes as MachdepBleakClient, then have a class BleakClient inheriting from those two. The AbstractBleakClient could then be annotated with the types and documentation, I have the feeling that would address #822 and #833 too.

[dlech]

I would like to have at least BleakClient available within bleak, in other words: move the platform-dependent imports from __init__.py to a new module (say api.py). __init__.py would then import them from there, but so could other modules within bleak.

I am in favor of this from a documentation point of view. If we do this, we can document all of the os-specific quirks in one place instead of having 5 copies of the documentation for each method (base, windows, mac, linux, android). I am also in favor of this from an intellesense point of view. The MS VS Code Python tools always pick up the Windows backend no matter which OS is actually being used.