Skip to content
Snippets Groups Projects
Commit 3cf0c527 authored by André Anjos's avatar André Anjos :speech_balloon:
Browse files

Merge branch 'doc-fix' into 'master'

Fix buildout code-block guesses

See merge request !107
parents 0425e8da 6329e034
No related branches found
No related tags found
1 merge request!107Fix buildout code-block guesses
Pipeline #35953 passed
......@@ -44,7 +44,7 @@ locally:
$ cd awesome-project
$ vi buildout.cfg
.. code-block:: guess
.. code-block:: cfg
[buildout]
parts = scripts
......@@ -236,7 +236,7 @@ from source:
Create a file named ``buildout.cfg`` in the ``awesome-project`` folder with the
following contents:
.. code-block:: guess
.. code-block:: cfg
[buildout]
parts = scripts
......@@ -353,7 +353,7 @@ packages, which will be build in exactly the order that you specified. With
this option, you can tell buildout particularly, in which directories it should
look for some packages.
.. code-block:: guess
.. code-block:: cfg
[buildout]
parts = scripts
......
......@@ -24,7 +24,7 @@ existing one. The guide heavily relies on the use of Python `setuptools`_ and
You should also go through the `new package instructions`_ page when creating a new
package. It is a step-by-step guide on how to setup your package, and in particular
contains various templates that you must use. Among other stuff, you will find
templates for ``README.rst``, ``setup.py``, ``buildout.cfg`` files,
templates for ``README.rst``, ``setup.py``, ``buildout.cfg`` files,
for continuous integration and for the conda recipe of your package.
Anatomy of a package
......@@ -135,7 +135,7 @@ To be able to use the package, we first need to build and install it locally.
This is explained in detail in :ref:`bob.extension.build_locally`.
The buildout configuration file of the package looks like:
.. code-block:: guess
.. code-block:: cfg
[buildout]
parts = scripts
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment