From 5e5c917081770fb5dbfdfc1f79c9f1d275d3bc28 Mon Sep 17 00:00:00 2001 From: Tyler Goodlet Date: Mon, 21 Jan 2019 11:59:44 -0500 Subject: [PATCH] Fix run_in_excutor() link --- README.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.rst b/README.rst index 3e16684..dfd7466 100644 --- a/README.rst +++ b/README.rst @@ -193,7 +193,7 @@ What's going on? much like you'd expect from a future_. This ``run_in_actor()`` API should look very familiar to users of -``asyncio``'s run_in_executor_ which uses a ``concurrent.futures`` Executor_. +``asyncio``'s `run_in_executor()`_ which uses a ``concurrent.futures`` Executor_. Since you might also want to spawn long running *worker* or *daemon* actors, each actor's *lifetime* can be determined based on the spawn @@ -258,7 +258,7 @@ to all others with ease over standard network protocols). .. _nursery: https://trio.readthedocs.io/en/latest/reference-core.html#nurseries-and-spawning .. _causal: https://vorpus.org/blog/some-thoughts-on-asynchronous-api-design-in-a-post-asyncawait-world/#causality .. _cancelled: https://trio.readthedocs.io/en/latest/reference-core.html#child-tasks-and-cancellation -.. _run_in_executor: https://docs.python.org/3/library/asyncio-eventloop.html#executor +.. _run_in_executor(): https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor .. _Executor: https://docs.python.org/3/library/concurrent.futures.html#concurrent.futures.Executor