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
For now the documentation is pretty scarce but we will be improving it with
time.
Upgrading (breaking changes)
You need to make sure to use timezone-awaredatetime objects when using
the timestamp returned by Timer, Otherwise you will get an exception.
Channels methods get_receiver() and get_sender() have been renamed to new_receiver() and new_sender() respectively. This is to make it more
clear that new objects are being created.
The public API surface has been reduced considerably to make it more clear
where to import symbols. You should update your imports. The new symbol
locations are:
frequenz.channels.Anycast
frequenz.channels.Broadcast
frequenz.channels.Anycast
frequenz.channels.Bidirectional
frequenz.channels.Broadcast
frequenz.channels.Peekable
frequenz.channels.Receiver
frequenz.channels.Sender
frequenz.channels.util.Merge
frequenz.channels.util.MergeNamed
frequenz.channels.util.FileWatcher
frequenz.channels.util.Select
frequenz.channels.util.Timer
The class BufferedReceiver was removed because the interface was really
intended for channel implementations. Users are not supposed to enqueue
messages to receiver but just receive from them. If you used it you can
implement it yourself.
The class BidirectionalHandle was moved to Bidirectional.Handle.
The class EventType was moved to FileWatcher.EventType.
New Features
Python 3.11 is now supported!
Bug Fixes
Broadcast receivers now get cleaned up once they go out of scope.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Frequenz Channels Release Notes
Summary
The project has a new home!
https://frequenz-floss.github.io/frequenz-channels-python/
For now the documentation is pretty scarce but we will be improving it with
time.
Upgrading (breaking changes)
You need to make sure to use timezone-aware
datetime
objects when usingthe timestamp returned by
Timer
, Otherwise you will get an exception.Channels methods
get_receiver()
andget_sender()
have been renamed tonew_receiver()
andnew_sender()
respectively. This is to make it moreclear that new objects are being created.
The public API surface has been reduced considerably to make it more clear
where to import symbols. You should update your imports. The new symbol
locations are:
frequenz.channels.Anycast
frequenz.channels.Broadcast
frequenz.channels.Anycast
frequenz.channels.Bidirectional
frequenz.channels.Broadcast
frequenz.channels.Peekable
frequenz.channels.Receiver
frequenz.channels.Sender
frequenz.channels.util.Merge
frequenz.channels.util.MergeNamed
frequenz.channels.util.FileWatcher
frequenz.channels.util.Select
frequenz.channels.util.Timer
The class
BufferedReceiver
was removed because the interface was reallyintended for channel implementations. Users are not supposed to enqueue
messages to receiver but just receive from them. If you used it you can
implement it yourself.
The class
BidirectionalHandle
was moved toBidirectional.Handle
.The class
EventType
was moved toFileWatcher.EventType
.New Features
Bug Fixes
Broadcast
receivers now get cleaned up once they go out of scope.Timer
now returns timezone-awaredatetime
objects using UTC astimezone.
What's Changed
version:xxx
and addpart:select
andpart:receivers
labels by @leandro-lucarella-frequenz in Removeversion:xxx
and addpart:select
andpart:receivers
labels #28Select
blocks by @shsms in Avoid dropping of messages after breaking fromSelect
blocks #42get_{sender,receiver}
tonew_{sender,receiver}
by @leandro-lucarella-frequenz in Renameget_{sender,receiver}
tonew_{sender,receiver}
#49changes
by @leandro-lucarella-frequenz in FileWatcher: Don't type-checkchanges
#56Full Changelog: v0.10.0...v0.11.0
This discussion was created from the release v0.11.0.
Beta Was this translation helpful? Give feedback.
All reactions