From 2315ffb0387927904b17a8943c0c67c3985c997c Mon Sep 17 00:00:00 2001 From: "Nathaniel J. Smith" Date: Sat, 13 Oct 2018 04:08:00 -0700 Subject: [PATCH] Belatedly fix a bunch of small issues in the v0.9.0 release note --- docs/source/history.rst | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/docs/source/history.rst b/docs/source/history.rst index 7bafee076c..945f7b7848 100644 --- a/docs/source/history.rst +++ b/docs/source/history.rst @@ -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 `__)