Skip to content

Commit 921ba08

Browse files
committed
docs: fix code blocks
1 parent b22aa91 commit 921ba08

1 file changed

Lines changed: 4 additions & 12 deletions

File tree

docs/oxidized_importer_getting_started.rst

Lines changed: 4 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,7 @@ Installing from PyPI
1919

2020
``oxidized_importer`` is
2121
`available <https://pypi.org/project/oxidized_importer/>`_ on PyPI. This
22-
means that installing is as simple as:
23-
24-
.. code-block::
22+
means that installing is as simple as::
2523

2624
$ pip3 install oxidized_importer
2725

@@ -30,9 +28,7 @@ Compiling from Source
3028

3129
To build from source, obtain a clone of PyOxidizer's Git repository and
3230
run the ``setup.py`` script or use ``pip`` to build the Python project in
33-
the root of the repository. e.g.
34-
35-
.. code-block::
31+
the root of the repository. e.g.::
3632

3733
$ python3.8 setup.py build_ext -i
3834
$ python3.8 setup.py install
@@ -42,18 +38,14 @@ the root of the repository. e.g.
4238

4339
The ``setup.py`` is pretty minimal and is a thin wrapper around ``cargo build``
4440
for the underlying Rust project. If you want to build using Rust's standard
45-
toolchain, do something like the following:
46-
47-
.. code-block::
41+
toolchain, do something like the following::
4842

4943
$ cd oxidized-importer
5044
$ cargo build --release
5145

5246
If you don't have a Python 3.8 ``python3`` executable in your ``PATH``, you
5347
will need to tell the Rust build system which ``python3`` executable to use to
54-
help derive the build configuration for the Python extension:
55-
56-
.. code-block::
48+
help derive the build configuration for the Python extension::
5749

5850
$ PYTHON_SYS_EXECUTABLE=/path/to/python3.8 cargo build
5951

0 commit comments

Comments
 (0)