Skip to content

Update changelog #727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bdraco merged 1 commit into from
Jun 18, 2021
Merged

Update changelog #727

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,25 +154,31 @@ Changelog
Python version eariler then 3.6 were likely broken with zeroconf
already, however the version is now explictly checked.

* BREAKING CHANGE: RecordUpdateListener now uses update_records instead of update_record (#419) @bdraco
* BREAKING CHANGE: RecordUpdateListener now uses async_update_records instead of update_record (#419, #726) @bdraco

This allows the listener to receive all the records that have
been updated in a single transaction such as a packet or
cache expiry.

update_record has been deprecated in favor of update_records
update_record has been deprecated in favor of async_update_records
A compatibility shim exists to ensure classes that use
RecordUpdateListener as a base class continue to have
update_record called, however they should be updated
as soon as possible.

A new method update_records_complete is now called on each
A new method async_update_records_complete is now called on each
listener when all listeners have completed processing updates
and the cache has been updated. This allows ServiceBrowsers
to delay calling handlers until they are sure the cache
has been updated as its a common pattern to call for
ServiceInfo when a ServiceBrowser handler fires.

The async_ prefix was choosen to make it clear that these
functions run in the eventloop and should never do blocking
I/O. Before 0.32+ these functions ran in a select() loop and
should not have been doing any blocking I/O, but it was not
clear to implementors that I/O would block the loop.

* BREAKING CHANGE: Ensure listeners do not miss initial packets if Engine starts too quickly (#387) @bdraco

When manually creating a zeroconf.Engine object, it is no longer started automatically.
Expand Down Expand Up @@ -231,6 +237,10 @@ Changelog

* MAJOR BUG: Fix queries for AAAA records (#616) @bdraco

* Fix ServiceInfo with multiple A records (#725) @bdraco

* Synchronize time for fate sharing (#718) @bdraco

* Cleanup typing in zero._core and document ignores (#714) @bdraco

* Cleanup typing in zeroconf._logger (#715) @bdraco
Expand Down