_uuid (str or UUID)

• bleak version: develop
• Python version: N/A
• Operating System: N/A

Description

There are several places in the documentation where there is a _uuid parameter. The docs say:

_uuid (str or UUID): The uuid of the characteristics to write to.

However, the type hints say: _uuid: str.

Looking at the actual code, in some cases, uuid.UUID is handled, but in others it is assumes that the parameter is a string, so when a pass a uuid.UUID, things crash.

Which is correct, the doc string or the type hints?

[5frank]

Just adding 2 cents to the discussion. Support for both uuid.UUID and str seems to add a lot of complexity and will sometimes get confusing. Example when using start_notify() with uuid.UUID but the callback (aka response_handler) is called with the same uuid as str. Would be nice if it was uuid.UUID as it provides better sanity check and comparison is not case sensitive.

[hbldh]

It can be done like this, yes, but the problem is not handling the comparisons. Thanks for the effort, but this will not add enough value to be worthwhile imo.