From a9b95ef598ab1efc7532eb910a04d406cf093152 Mon Sep 17 00:00:00 2001 From: "Nathaniel J. Smith" Date: Fri, 5 Oct 2018 00:35:46 -0700 Subject: [PATCH] Fix sphinx link --- newsfragments/497.feature.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/newsfragments/497.feature.rst b/newsfragments/497.feature.rst index 820b76471a..2f3e21b4b1 100644 --- a/newsfragments/497.feature.rst +++ b/newsfragments/497.feature.rst @@ -1,12 +1,12 @@ 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" objects, for consistency -with other communication interfaces like :class:`trio.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. +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.