J. Nick Koston

The first broadcast is sent right away https://github.com/jstasiak/python-zeroconf/blob/master/zeroconf/__init__.py#L2601 and then the subsequent ones are are delayed. Can you provide a little more detail about what you are waiting on?

The idea behind register time is that some devices may miss the first broadcast (wifi drops etc) If we don't wait between the broadcasts they may never see the announcement.

You could manually call the underlying functions to avoid the wait. Example: https://github.com/jstasiak/python-zeroconf/blob/master/zeroconf/asyncio.py#L85

this one needs to get solved first https://github.com/python-zeroconf/python-zeroconf/pull/1138 Happy to take a PR if you want to work on this.

Many of these warning have likely existed for the better part of a decade. I prioritize fixing errors and regressions so this one is far down on the list as...

A PR with the above would be great. I'm not sure about `gdb_debug` as it likely means we get even larger binaries https://cython.readthedocs.io/en/latest/src/userguide/debugging.html

I've talked to the major contributors and so far there is general agreement that switching to Apache 2.0 to MIT would be fine. We would need to do a more...

https://python-semantic-release.readthedocs.io/en/latest/migrating_from_v7.html

Try `examples % python3 async_browser.py --find` instead

It really doesn't matter so much until we solve https://github.com/python-zeroconf/python-zeroconf/issues/821