From 0e95c887da35f37d16e9903d8ef4ee74eaacf837 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Mon, 30 Aug 2021 16:14:29 +0200 Subject: dev-manual: explicit that devpyshell is a task Without this, readers could think that "devpyshell" is a script, at least until they read the remainder of the section. (From yocto-docs rev: fe1e3323a633acf51d64cfb6c4bdd2ecd324a79e) Signed-off-by: Michael Opdenacker Reviewed-by: Quentin Schulz Signed-off-by: Richard Purdie --- documentation/dev-manual/common-tasks.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst index 1acca8e64c..25e6b085e5 100644 --- a/documentation/dev-manual/common-tasks.rst +++ b/documentation/dev-manual/common-tasks.rst @@ -3476,7 +3476,7 @@ Similar to working within a development shell as described in the previous section, you can also spawn and work within an interactive Python development shell. When debugging certain commands or even when just editing packages, ``devpyshell`` can be a useful tool. When you -invoke ``devpyshell``, all tasks up to and including +invoke the ``devpyshell`` task, all tasks up to and including :ref:`ref-tasks-patch` are run for the specified target. Then a new terminal is opened. Additionally, key Python objects and code are available in the same way they are to -- cgit v1.2.3-54-g00ecf