summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Opdenacker <michael.opdenacker@bootlin.com>2021-10-18 17:05:33 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-10-20 20:22:20 +0100
commit07108739ce3283576e2041d6b399c9a21b579f6d (patch)
tree9023dd8c6fa5a2d1e3e4d3cce7b3f77feeaae72f
parent5550d83ff7a9a2ad213bad7ba06c3b77835e815d (diff)
downloadpoky-07108739ce3283576e2041d6b399c9a21b579f6d.zip
poky-07108739ce3283576e2041d6b399c9a21b579f6d.tar.gz
poky-07108739ce3283576e2041d6b399c9a21b579f6d.tar.bz2
manuals: rename "devpyshell" to "pydevshell"
This addresses [YOCTO #14531] after the "devpyshell" task was renamed to "pydevshell" in OE core. (From yocto-docs rev: 1056320e90545c8dff0fc71a5fde752295d4d6e4) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/common-tasks.rst12
-rw-r--r--documentation/ref-manual/tasks.rst8
2 files changed, 10 insertions, 10 deletions
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index 4683b1c..3eead14 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -3531,14 +3531,14 @@ terminal window.
- It is also worth noting that ``devshell`` still works over X11
forwarding and similar situations.
-Using a Development Python Shell
+Using a Python Development Shell
================================
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 the ``devpyshell`` task, all tasks up to and including
+just editing packages, ``pydevshell`` can be a useful tool. When you
+invoke the ``pydevshell`` 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
@@ -3563,17 +3563,17 @@ system were executing them. Consequently, working this way can be
helpful when debugging a build or preparing software to be used with the
OpenEmbedded build system.
-Following is an example that uses ``devpyshell`` on a target named
+Following is an example that uses ``pydevshell`` on a target named
``matchbox-desktop``::
- $ bitbake matchbox-desktop -c devpyshell
+ $ bitbake matchbox-desktop -c pydevshell
This command spawns a terminal and places you in an interactive Python
interpreter within the OpenEmbedded build environment. The
:term:`OE_TERMINAL` variable
controls what type of shell is opened.
-When you are finished using ``devpyshell``, you can exit the shell
+When you are finished using ``pydevshell``, you can exit the shell
either by using Ctrl+d or closing the terminal window.
Building
diff --git a/documentation/ref-manual/tasks.rst b/documentation/ref-manual/tasks.rst
index 4edae33..299969d 100644
--- a/documentation/ref-manual/tasks.rst
+++ b/documentation/ref-manual/tasks.rst
@@ -516,17 +516,17 @@ scratch is guaranteed.
$ bitbake -f -c do_cleansstate target
-.. _ref-tasks-devpyshell:
+.. _ref-tasks-pydevshell:
-``do_devpyshell``
+``do_pydevshell``
-----------------
Starts a shell in which an interactive Python interpreter allows you to
interact with the BitBake build environment. From within this shell, you
can directly examine and set bits from the data store and execute
-functions as if within the BitBake environment. See the ":ref:`dev-manual/common-tasks:using a development python shell`" section in
+functions as if within the BitBake environment. See the ":ref:`dev-manual/common-tasks:using a python development shell`" section in
the Yocto Project Development Tasks Manual for more information about
-using ``devpyshell``.
+using ``pydevshell``.
.. _ref-tasks-devshell: