Skip to content

gh-125403: fix console formatting in Chapter 12 of the tutorial #125404

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 13, 2024
Merged

gh-125403: fix console formatting in Chapter 12 of the tutorial #125404

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions Doc/tutorial/venv.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ virtual environment you're using, and modify the environment so that running
``python`` will get you that particular version and installation of Python.
For example:

.. code-block:: bash
.. code-block:: console
$ source ~/envs/tutorial-env/bin/activate
(tutorial-env) $ python
Expand Down Expand Up @@ -108,7 +108,7 @@ complete documentation for ``pip``.)

You can install the latest version of a package by specifying a package's name:

.. code-block:: bash
.. code-block:: console
(tutorial-env) $ python -m pip install novas
Collecting novas
Expand All @@ -120,7 +120,7 @@ You can install the latest version of a package by specifying a package's name:
You can also install a specific version of a package by giving the
package name followed by ``==`` and the version number:

.. code-block:: bash
.. code-block:: console
(tutorial-env) $ python -m pip install requests==2.6.0
Collecting requests==2.6.0
Expand All @@ -133,7 +133,7 @@ version is already installed and do nothing. You can supply a
different version number to get that version, or you can run ``python
-m pip install --upgrade`` to upgrade the package to the latest version:

.. code-block:: bash
.. code-block:: console
(tutorial-env) $ python -m pip install --upgrade requests
Collecting requests
Expand All @@ -148,7 +148,7 @@ remove the packages from the virtual environment.

``python -m pip show`` will display information about a particular package:

.. code-block:: bash
.. code-block:: console
(tutorial-env) $ python -m pip show requests
---
Expand All @@ -166,7 +166,7 @@ remove the packages from the virtual environment.
``python -m pip list`` will display all of the packages installed in
the virtual environment:

.. code-block:: bash
.. code-block:: console
(tutorial-env) $ python -m pip list
novas (3.1.1.3)
Expand All @@ -179,7 +179,7 @@ the virtual environment:
but the output uses the format that ``python -m pip install`` expects.
A common convention is to put this list in a ``requirements.txt`` file:

.. code-block:: bash
.. code-block:: console
(tutorial-env) $ python -m pip freeze > requirements.txt
(tutorial-env) $ cat requirements.txt
Expand All @@ -191,7 +191,7 @@ The ``requirements.txt`` can then be committed to version control and
shipped as part of an application. Users can then install all the
necessary packages with ``install -r``:

.. code-block:: bash
.. code-block:: console
(tutorial-env) $ python -m pip install -r requirements.txt
Collecting novas==3.1.1.3 (from -r requirements.txt (line 1))
Expand Down
Loading