Skip to content
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

Belatedly fix a bunch of small issues in the v0.9.0 release note #734

Merged
merged 1 commit into from
Oct 14, 2018
Merged

Belatedly fix a bunch of small issues in the v0.9.0 release note #734

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
18 changes: 10 additions & 8 deletions docs/source/history.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,14 +14,16 @@ Features
- New and improved APIs for inter-task communication:
:class:`trio.abc.SendChannel`, :class:`trio.abc.ReceiveChannel`, and
:func:`trio.open_memory_channel` (which replaces ``trio.Queue``). This
interface uses separate "send" and "receive" methods, for consistency with
other communication interfaces like :class:`~trio.abc.Stream`. Also, the two
objects can now be closed individually, making it much easier to gracefully
shut down a channel. Also, check out the nifty ``clone`` API to make it easy
to manage fan-in scenarios. Also, the API has been written to allow for
future channel-like objects that send objects across process boundaries.
Also, it supports unbounded buffering if you really need it. Also, help I
can't stop writing also. See :ref:`channels` for more details. (`#497
interface uses separate "sender" and "receiver" objects, for
consistency with other communication interfaces like
:class:`~trio.abc.Stream`. Also, the two objects can now be closed
individually, making it much easier to gracefully shut down a channel.
Also, check out the nifty ``clone`` API to make it easy to manage
shutdown in multiple-producer/multiple-consumer scenarios. Also, the
API has been written to allow for future channel implementations that
send objects across process boundaries. Also, it supports unbounded
buffering if you really need it. Also, help I can't stop writing also.
See :ref:`channels` for more details. (`#497
<https://github.com/python-trio/trio/issues/497>`__)


Expand Down