You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Technically speaking, BleakScanner.get_disovered_devices() does not need to be async since none of the implementations await anything.
However, changing it would be a major breaking change. We could probably lessen the impact by doing something similar to bc6da1e to make it not quite so breaking if we decide it is worth making the change (for some time, it would return an object that is both a list and a future that gives a warning about the change).
The text was updated successfully, but these errors were encountered:
Yes, I agree. It absolutely does not need to be async. It should be changed. Apply the same warning procedure and let's try to get it properly changed in a future release.
This adds a new `BleakScanner.discovered_devices` property to replace
the `BleakScanner.get_discovered_devices()` async method.
A deprecation warning is added to `BleakScanner.get_discovered_devices()`
and the documentation for that method.
Fixes#489
Technically speaking,
BleakScanner.get_disovered_devices()
does not need to be async since none of the implementations await anything.However, changing it would be a major breaking change. We could probably lessen the impact by doing something similar to bc6da1e to make it not quite so breaking if we decide it is worth making the change (for some time, it would return an object that is both a list and a future that gives a warning about the change).
The text was updated successfully, but these errors were encountered: